Horton

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

Justin Pryzby <pryzby@telsasoft.com>

View thread View on postgr.es
From: Justin Pryzby <pryzby@telsasoft.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>, Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org, Dilip Kumar <dilipbalaut@gmail.com>, Robert Haas <robertmhaas@gmail.com>
Date: 2021-05-26T01:33:47Z
Lists: pgsql-hackers 
On Sun, May 23, 2021 at 12:25:10PM -0400, Tom Lane wrote:
> However, the more I looked at that code the less I liked it.
> I think the way that compression selection is handled for indexes,
> ie consult default_toast_compression on-the-fly, is *far* saner
> than what is currently implemented for tables.  So I think we
> should redefine attcompression as "ID of a compression method
> to use, or \0 to select the prevailing default.  Ignored if
> attstorage does not permit the use of compression".

+1

It reminds me of reltablespace, which is stored as 0 to mean the database's
default tablespace.

Also, values are currently retoasted during vacuum full if their column's
current compression method doesn't match the value's old compression.

But it doesn't rewrite the column if the it used to use the default
compression, and the default was changed.  I think your idea would handle that.

-- 
Justin

PS. I just ran into the memory leak that Andres reported and Michael fixed.

Commits

  1. Remove forced toast recompression in VACUUM FULL/CLUSTER

  2. Rethink definition of pg_attribute.attcompression.

  3. Fix memory leak when de-toasting compressed values in VACUUM FULL/CLUSTER

  4. Re-order pg_attribute columns to eliminate some padding space.

  5. Add more TAP tests for pg_dump with attribute compression