Re: Removing vacuum_cleanup_index_scale_factor

Masahiko Sawada <sawada.mshk@gmail.com>

From: Masahiko Sawada <sawada.mshk@gmail.com>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-03-11T02:00:38Z
Lists: pgsql-hackers
On Thu, Mar 11, 2021 at 10:12 AM Peter Geoghegan <pg@bowt.ie> wrote:
>
> On Tue, Mar 9, 2021 at 7:42 PM Peter Geoghegan <pg@bowt.ie> wrote:
> > My current plan is to commit everything within the next day or two.
> > This includes backpatching to Postgres 13 only.
>
> Pushed, thanks.

Great! Thank you!

Regards,

-- 
Masahiko Sawada
EDB:  https://www.enterprisedb.com/



Commits

  1. VACUUM ANALYZE: Always update pg_class.reltuples.

  2. Don't consider newly inserted tuples in nbtree VACUUM.

  3. Fix nbtree cleanup-only VACUUM stats inaccuracies.

  4. Disable recheck_on_update optimization to avoid crashes.

  5. Fix VACUUM so that it always updates pg_class.reltuples/relpages.

  6. Clean up API for ambulkdelete/amvacuumcleanup as per today's discussion.

  7. First steps towards statistics on expressional (nee functional) indexes.