Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?
Date
Msg-id 14058.1244732738@sss.pgh.pa.us
Whole thread Raw
In response to Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Greg Stark <stark@enterprisedb.com> wrote:
>> You could use "ALTER COLUMN SET STORAGE PLAIN" to disable toasting on
>> that column entirely. This will disable compression as well though.
> 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 kinda doubt the OP wants it to fail outright for rows over 8K,
so altering TOAST_TUPLE_THRESHOLD seems like the right answer.
Too bad we don't have that set up as a reloption...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Shadar
Date:
Subject: Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?
Next
From: Greg Stark
Date:
Subject: Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?