From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Alvaro Herrera <alvherre(at)atentus(dot)com>, PgSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: TOAST docs |
Date: | 2002-09-13 16:46:08 |
Message-ID: | 3D821650.8090208@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hannu Krosing wrote:
> IIRC there were some ways to tweak when TOAST gets used, when it goes
> out to toastfile and when it uses compressed/non-compressed storage.
>
> I hope this is documented someplace, no ?
There is a mention of it in the ALTER TABLE doc:
ALTER TABLE [ ONLY ] table [ * ]
ALTER [ COLUMN ] column SET STORAGE { PLAIN | EXTERNAL | EXTENDED | MAIN }
SET STORAGE
This form sets the storage mode for a column. This controls whether this
column is held inline or in a supplementary table, and whether the data should
be compressed or not. PLAIN must be used for fixed-length values such as
INTEGER and is inline, uncompressed. MAIN is for inline, compressible data.
EXTERNAL is for external, uncompressed data and EXTENDED is for external,
compressed data. EXTENDED is the default for all datatypes that support it.
The use of EXTERNAL will make substring operations on a TEXT column faster, at
the penalty of increased storage space.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2002-09-13 16:59:49 | Re: Multicolumn foreign keys need useless unique indices? |
Previous Message | Hannu Krosing | 2002-09-13 16:44:43 | Re: TOAST docs |