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

From Kevin Grittner
Subject Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?
Date
Msg-id 4A30D5370200002500027897@gw.wicourts.gov
Whole thread Raw
In response to Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?  (Greg Stark <stark@enterprisedb.com>)
Responses Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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.
If
> any record doesn't fit in an 8kB block you'll get an error.
> 
> Alternately you could leave the column alone but drop the toast
table
> (presumably having truncated the table first). That will leave
> compression enabled but force the system to avoid storing things
> externally. Again you'll get an error if a record doesn't fit in 8kB
> but only after first trying to compress the data.
Why not use "ALTER COLUMN SET STORAGE MAIN", to allow compression but
avoid external storage?
http://www.postgresql.org/docs/8.3/interactive/sql-altertable.html
-Kevin


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?
Next
From: Tom Lane
Date:
Subject: Re: pgindent run coming