Re: Move pg_attribute.attcompression to earlier in struct for reduced size?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Move pg_attribute.attcompression to earlier in struct for reduced size?
Date: 2021-05-27 04:04:38
Message-ID: YK8aVuS0+8JOe8IM@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2021-05-27 04:05:37 Re: Decoding speculative insert with toast leaks memory
Previous Message Amit Kapila 2021-05-27 03:56:40 Re: Decoding speculative insert with toast leaks memory