Re: Repair cosmetic damage (done by pg_indent?)

On Fri, Jul 27, 2007 at 04:07:01PM +0100, Gregory Stark wrote:
> Fwiw, do we really not want to compress anything smaller than 256 bytes
> (everyone in Postgres uses the default strategy, not the always strategy).

Is there actually a way to specify always compressing? I'm not seeing it
on http://www.postgresql.org/docs/8.2/interactive/storage-toast.html

> ISTM that with things like CHAR(n) around we might very well have some
> databases where compression for smaller sized datums would be beneficial. I
> would suggest 32 for the minimum.

CPU is generally cheaper than IO now-a-days, so I agree with something
less than 256. Not sure what would be best though.

I do have a database that has both user-entered information as well as
things like email addresses, so I could do some testing on that if
people want.
--
Decibel!, aka Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)