From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
---|---|
To: | Stef <svb(at)ucs(dot)co(dot)za> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Compression of text columns |
Date: | 2005-10-10 12:27:14 |
Message-ID: | 434A5E22.9040500@wildenhain.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Stef schrieb:
> I have a table in the databases I work with,
> that contains two text columns with XML data
> stored inside them.
>
> This table is by far the biggest table in the databases,
> and the text columns use up the most space.
> I saw that the default storage type for text columns is
> "EXTENDED" which, according to the documentation, uses up extra
> space to make possible substring functioning faster.
>
> Suppose that the data in those columns are only really ever
> _used_ once, but may be needed in future for viewing purposes mostly,
> and I cannot really change the underlying structure of the table,
> what can I possibly do to maximally reduce the amount of disk space
> used by the table on disk. (There are no indexes on these two columns.)
> I've thought about compression using something like :
> ztext http://www.mahalito.net/~harley/sw/postgres/
>
> but I have to change the table structure a lot and I've already
> encountered problems unzipping the data again.
> The other problem with this solution, is that database dumps almost double
> in size, because of double compression.
>
> Any suggestions much appreciated
Well, text columns are automatically compressed via the toast mechanism.
This is handled transparently for you.
From | Date | Subject | |
---|---|---|---|
Next Message | Steinar H. Gunderson | 2005-10-10 12:54:22 | Re: Text/Varchar performance... |
Previous Message | Stef | 2005-10-10 12:17:21 | Compression of text columns |