Re: pgsql: Don't consider newly inserted tuples in nbtree VACUUM.

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Don't consider newly inserted tuples in nbtree VACUUM.
Date: 2021-03-11 07:08:39
Message-ID: CAH2-WznS5S0HhjR_3CorPZHdWCz1G3tg73hjN8YiwSWP=bTQrw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Mar 10, 2021 at 10:57 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> I think that this commit has some issues that need more thoughts.
>
> The removal of vacuum_cleanup_index_scale_factor means that any
> existing deployment of Postgres that includes at least one index using
> this parameter would fail in the middle of the restore during
> pg_upgrade, when restoring the binary dump.

I don't believe that it's necessary. Partly because it seems rather
unlikely that vacuum_cleanup_index_scale_factor was ever set like this
in practice.

You could have made the same arguments against removing
recheck_on_update in commit 1c53c4de.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2021-03-11 07:33:42 pgsql: Drop other index behind pg_upgrade test issue.
Previous Message Michael Paquier 2021-03-11 06:57:47 Re: pgsql: Don't consider newly inserted tuples in nbtree VACUUM.