Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?

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

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.
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-06-11 15:00:13 Re: pgindent run coming
Previous Message Greg Stark 2009-06-11 14:54:23 Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?