Re: Teaching users how they can get the most out of HOT in Postgres 14
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-05-13T07:27:47Z
Lists: pgsql-hackers
Attachments
- vacuum-index-cleanup-v1.patch (text/x-diff) patch v1
On Tue, May 11, 2021 at 04:42:27PM +0900, Michael Paquier wrote: > Whatever the solution chosen, the thing I can see we agree on here is > that we need to do something, at least in the shape of an on/off > switch to have an escape path in case of problems. Peter, could we > get something by beta1 for that? FWIW, I would use a float GUC to > control that, and not a boolean switch, but I am just one voice here, > and that's not a feature I worked on. So, I have been thinking more about this item, and a boolean switch still sounded weird to me, so attached is a patch to have two GUCs, one for manual VACUUM and autovacuum like any other parameters, to control this behavior, with a default set at 2% of the number of relation pages with dead items needed to do the index cleanup work. Even if we switch the parameter type used here, the easiest and most consistent way to pass down the parameter is just to use VacuumParams set within ExecVacuum() and the autovacuum code path. The docs need more work, I guess. Thoughts? -- Michael
Commits
-
Support disabling index bypassing by VACUUM.
- 3499df0dee8c 14.0 landed
-
Teach VACUUM to bypass unnecessary index vacuuming.
- 5100010ee4d5 14.0 cited