Re: Behavior change in PostgreSQL 14Beta3 or bug? - Mailing list pgsql-general

From Tom Lane
Subject Re: Behavior change in PostgreSQL 14Beta3 or bug?
Date
Msg-id 3065647.1630943989@sss.pgh.pa.us
Whole thread Raw
In response to Re: Behavior change in PostgreSQL 14Beta3 or bug?  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Behavior change in PostgreSQL 14Beta3 or bug?  (Laurenz Albe <laurenz.albe@cybertec.at>)
Re: Behavior change in PostgreSQL 14Beta3 or bug?  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-general
Laurenz Albe <laurenz.albe@cybertec.at> writes:
> It is not an incompatibility that warrants a mention in the release notes,
> but perhaps somthing in
> https://www.postgresql.org/docs/14/indexes-index-only-scans.html
> and/or
> https://www.postgresql.org/docs/14/routine-vacuuming.html#VACUUM-FOR-VISIBILITY-MAP
> could be added that recommends that people should consider frequent
> VACUUM with "index_cleanup = on" for best performance with index-only scans.

If enough pages would change their all-visible state to make a significant
difference in index-only scan performance, VACUUM should not be skipping
the cleanup.  If it is, the threshold for that is too aggressive.

Assuming that that choice was made appropriately, I think the advice you
propose here will just cause people to waste lots of cycles on VACUUM
runs that have only marginal effects.

            regards, tom lane



pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Behavior change in PostgreSQL 14Beta3 or bug?
Next
From: Laurenz Albe
Date:
Subject: Re: Behavior change in PostgreSQL 14Beta3 or bug?