| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Jonathan Ellis <jonathan(at)utahpython(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: forcing compression of text field |
| Date: | 2006-12-11 23:00:43 |
| Message-ID: | 1165878043.13508.10.camel@dogma.v10.wvs |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2006-12-11 at 09:18 -0700, Jonathan Ellis wrote:
> I have a table of log messages. They are mostly in the 100-200
> character length, which apparently isn't large enough for PG to want
> to compress it (length == octet_length). I really need to save disk
> space. I can store it as a bytea and compress it manually (zlib level
> 1 compression gives about 50% savings), but is there a way to force
> pg's own compression before I resort to this?
>
Are you sure PostgreSQL isn't compressing it? I didn't think there was a
minimum threshold for compression.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | SCassidy | 2006-12-11 23:05:54 | Re: shell script to populate array values |
| Previous Message | Bruce Momjian | 2006-12-11 22:48:35 | Re: concatenation operator || with "null" array |