From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Compression hacks? |
Date: | 2011-02-25 07:21:15 |
Message-ID: | 4D67586B.7040805@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/24/11 10:55 PM, Yang Zhang wrote:
> For various workloads, compression could be a win on both disk space
> and speed (see, e.g.,
> http://blog.oskarsson.nu/2009/03/hadoop-feat-lzo-save-disk-space-and.html)
> I realize Postgresql doesn't have general table compression a la
> InnoDB's row_format=compressed (there's TOAST for large values and
> there's some old discussion on
> http://wiki.postgresql.org/wiki/CompressedTables) but I thought I'd
> ask: anybody tried to compress their PG data somehow? E.g., any
> positive experiences running PG on a compressed filesystem (and any
> caveats)? Anecdotal stories of the effects of app-level large-field
> compression in analytical workloads (though I'd be curious about
> transactional workloads as well)? Thanks in advance.
compressed file systems tend to perform poorly on random 8K block
writes, which transactional databases do a lot of.
From | Date | Subject | |
---|---|---|---|
Next Message | Vibhor Kumar | 2011-02-25 07:30:06 | Re: PostgreSQL group sort |
Previous Message | Yang Zhang | 2011-02-25 06:55:23 | Compression hacks? |