Re: Move pg_attribute.attcompression to earlier in struct for reduced size? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Move pg_attribute.attcompression to earlier in struct for reduced size?
Date
Msg-id 1687119.1622088698@sss.pgh.pa.us
Whole thread Raw
In response to Re: Move pg_attribute.attcompression to earlier in struct for reduced size?  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Move pg_attribute.attcompression to earlier in struct for reduced size?
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Wed, May 26, 2021 at 11:34:53PM -0400, Tom Lane wrote:
>> So maybe we should just dump the promise that VACUUM FULL will recompress
>> everything?  I'd be in favor of that actually, because it seems 100%
>> outside the charter of either VACUUM FULL or CLUSTER.

> Hmm.  You are right that by default this may not be worth the extra
> cost.  We could make that easily an option, though, for users ready to
> accept this cost.  And that could be handy when it comes to a
> database-wise VACUUM.

AFAIR, there are zero promises about how effective, or when effective,
changes in SET STORAGE will be.  And the number of complaints about
that has also been zero.  So I'm not sure why we need to do more for
SET COMPRESSION.  Especially since I'm unconvinced that recompressing
everything just to recompress everything would *ever* be worthwhile.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Decoding speculative insert with toast leaks memory
Next
From: Amit Kapila
Date:
Subject: Re: Parallel Inserts in CREATE TABLE AS