From: | Decibel! <decibel(at)decibel(dot)org> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Repair cosmetic damage (done by pg_indent?) |
Date: | 2007-07-28 17:57:40 |
Message-ID: | 20070728175740.GD25704@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
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)
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-07-29 11:06:50 | Re: Repair cosmetic damage (done by pg_indent?) |
Previous Message | Magnus Hagander | 2007-07-27 20:01:06 | Re: [PATCHES] patch win32.mak of libpq |