Re: Compression - Mailing list pgsql-general

From Yang Zhang
Subject Re: Compression
Date
Msg-id BANLkTinUMVpVWFO7-iDoZ5nu3sqw3_FiEw@mail.gmail.com
Whole thread Raw
In response to Re: Compression  ("mark" <dvlhntr@gmail.com>)
List pgsql-general
On Thu, Apr 14, 2011 at 6:46 PM, mark <dvlhntr@gmail.com> wrote:
>
>
>> -----Original Message-----
>> From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-
>> owner@postgresql.org] On Behalf Of Yang Zhang
>> Sent: Thursday, April 14, 2011 6:51 PM
>> To: Adrian Klaver
>> Cc: pgsql-general@postgresql.org; Craig Ringer
>> Subject: Re: [GENERAL] Compression
>>
>> On Thu, Apr 14, 2011 at 5:07 PM, Adrian Klaver
>> <adrian.klaver@gmail.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.klaver@gmail.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@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>
>



--
Yang Zhang
http://yz.mit.edu/

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Compression
Next
From: Craig Ringer
Date:
Subject: Re: Compression