From: | Yang Zhang <yanghatespam(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Subject: | Re: Compression |
Date: | 2011-04-15 00:51:21 |
Message-ID: | BANLkTim3LqeHZpfF=URwY4iARhwiVHkHkQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
--
Yang Zhang
http://yz.mit.edu/
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksey Tsalolikhin | 2011-04-15 01:12:16 | How can you have an Exclusive Lock on nothing? please help me understand this lock monitoring query output |
Previous Message | Adrian Klaver | 2011-04-15 00:07:43 | Re: Compression |