Re: [HACKERS] Custom compression methods - Mailing list pgsql-hackers

From Евгений Шишкин
Subject Re: [HACKERS] Custom compression methods
Date
Msg-id 2488A5D0-9C39-48D1-A059-28CB99332B48@gmail.com
Whole thread Raw
In response to Re: [HACKERS] Custom compression methods  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: [HACKERS] Custom compression methods  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers

> On Nov 20, 2017, at 18:29, Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote:
>
>>
>> What about instead of dropping column we leave data uncompressed?
>>
>
> That requires you to go through the data and rewrite the whole table.
> And I'm not aware of a DROP command doing that, instead they just drop
> the dependent objects (e.g. DROP TYPE, ...). So per PLOS the DROP
> COMPRESSION METHOD command should do that too.

Well, there is no much you can do with DROP TYPE. But i'd argue that compression
is different. We do not drop data in case of DROP STATISTICS or DROP INDEX.

At least there should be a way to easily alter compression method then.

pgsql-hackers by date:

Previous
From: Ildar Musin
Date:
Subject: IndexTupleDSize macro seems redundant
Next
From: Ildus Kurbangaliev
Date:
Subject: Re: [HACKERS] Custom compression methods