Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Greg Stark" <stark(at)enterprisedb(dot)com>, "Shadar" <shauldar(at)gmail(dot)com>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?
Date: 2009-06-11 15:24:11
Message-ID: 4A30DB4B02000025000278A4@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> Why not use "ALTER COLUMN SET STORAGE MAIN", to allow compression
>> but avoid external storage?
>
> That only discourages pushing a particular column out; it will still
> do so if the row exceeds TOAST_TUPLE_THRESHOLD after compression.

I thought that's the behavior of EXTENDED. The fine manual says "MAIN
allows compression but not out-of-line storage. (Actually, out-of-line
storage will still be performed for such columns, but only as a last
resort when there is no other way to make the row small enough.)"

If that doesn't mean that it will only use out-of-line storage when
the row doesn't fit in the page, then the manual could use a fix.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-06-11 15:41:22 Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?
Previous Message Alvaro Herrera 2009-06-11 15:18:14 Re: pgindent run coming