From: | Yang Zhang <yanghatespam(at)gmail(dot)com> |
---|---|
To: | mark <dvlhntr(at)gmail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Subject: | Re: Compression |
Date: | 2011-04-15 04:16:35 |
Message-ID: | BANLkTinUMVpVWFO7-iDoZ5nu3sqw3_FiEw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Apr 14, 2011 at 6:46 PM, mark <dvlhntr(at)gmail(dot)com> wrote:
>
>
>> -----Original Message-----
>> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-
>> owner(at)postgresql(dot)org] On Behalf Of Yang Zhang
>> Sent: Thursday, April 14, 2011 6:51 PM
>> To: Adrian Klaver
>> Cc: pgsql-general(at)postgresql(dot)org; Craig Ringer
>> Subject: Re: [GENERAL] Compression
>>
>> On Thu, Apr 14, 2011 at 5:07 PM, Adrian Klaver
>> <adrian(dot)klaver(at)gmail(dot)com> wrote:
>> > On Thursday, April 14, 2011 4:50:44 pm Craig Ringer wrote:
>> >
>> >> On 15/04/2011 7:01 AM, Yang Zhang wrote:
>> >
>> >> > Is there any effort to add compression into PG, a la MySQL's
>> >
>> >> > row_format=compressed or HBase's LZO block compression?
>> >
>> >>
>> >
>> >> There's no row compression, but as mentioned by others there is
>> >
>> >> out-of-line compression of large values using TOAST.
>> >
>> > I could be misunderstanding but I thought compression happened in the
>> row as
>> > well. From the docs:
>> >
>> > "EXTENDED allows both compression and out-of-line storage. This is
>> the
>> > default for most TOAST-able data types. Compression will be attempted
>> first,
>> > then out-of-
>> >
>> > line storage if the row is still too big. "
>> >
>> >>
>> >
>> >> Row compression would be interesting, but I can't imagine it not
>> having
>> >
>> >> been investigated already.
>> >
>> > --
>> >
>> > Adrian Klaver
>> >
>> > adrian(dot)klaver(at)gmail(dot)com
>>
>> Already know about TOAST. I could've been clearer, but that's not the
>> same as the block-/page-level compression I was referring to.
>
> There is a (closed source) PG fork that has row (or column) oriented storage
> that can have compression applied to them.... if you are willing to give up
> updates and deletes on the table that is.
Greenplum and Aster?
We *are* mainly doing analytical (non-updating/deleting) processing.
But it's not a critical pain point - we're mainly interested in FOSS
for now.
>
>
> I haven't seen a lot of people talking about wanting that in the Postgres
> core tho.
>
>
> -M
>
>>
>> --
>> Yang Zhang
>> http://yz.mit.edu/
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>
>
--
Yang Zhang
http://yz.mit.edu/
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2011-04-15 04:37:10 | Re: Compression |
Previous Message | Adrian Klaver | 2011-04-15 04:06:58 | Re: Compression |