Re: Move pg_attribute.attcompression to earlier in struct for reduced size?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
Robert Haas <robertmhaas@gmail.com>,
Justin Pryzby <pryzby@telsasoft.com>,
Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org,
Dilip Kumar <dilipbalaut@gmail.com>
Date: 2021-05-27T00:29:50Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes: > Yeah, having an extra test for partitioned tables would be a good > idea. We do have some coverage already via the pg_upgrade test. > Could it be possible to have some tests for COMPRESSION DEFAULT? It > seems to me that this should be documented as a supported keyword for > CREATE/ALTER TABLE. Uh, I did do both of those, no? (The docs treat "default" as another possible value, not a keyword, even though it's a keyword internally.) > --changing column storage should not impact the compression method > --but the data should not be compressed > ALTER TABLE cmdata2 ALTER COLUMN f1 TYPE varchar; > +ALTER TABLE cmdata2 ALTER COLUMN f1 SET COMPRESSION pglz; > This comment needs a refresh? It's correct AFAICS. Maybe it needs a bit of editing for clarity, but I'm not sure how to make it better. The point is that the SET STORAGE just below disables compression of new values, no matter what SET COMPRESSION says. regards, tom lane
Commits
-
Remove forced toast recompression in VACUUM FULL/CLUSTER
- dbab0c07e5ba 14.0 landed
-
Rethink definition of pg_attribute.attcompression.
- e6241d8e030f 14.0 landed
-
Fix memory leak when de-toasting compressed values in VACUUM FULL/CLUSTER
- fb0f5f0172ed 14.0 landed
-
Re-order pg_attribute columns to eliminate some padding space.
- f5024d8d7b04 14.0 landed
-
Add more TAP tests for pg_dump with attribute compression
- 63db0ac3f9e6 14.0 cited