| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| 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:05:38 |
| Message-ID: | 14058.1244732738@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Greg Stark <stark(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-06-11 15:08:44 | Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET? |
| Previous Message | Shadar | 2009-06-11 15:03:49 | Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET? |