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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: pgsql: Don't consider newly inserted tuples in nbtree VACUUM.
Date: 2021-03-11 03:04:38
Message-ID: CAH2-Wzmy1jO0jwm6Rnc3TooUat0Nx6P-sb6de8HWsdzAq1ebkg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Mar 10, 2021 at 5:49 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Perhaps the best solution is also the simplest: revert the tests for
> vacuum_cleanup_index_scale_factor storage on the backbranches
> (Postgres 12 and 13) too. The tests in question don't test much.

I just pushed a fix to REL_11_STABLE and REL_12_STABLE only. I decided
to drop the index with vacuum_cleanup_index_scale_factor set (which is
a more targeted fix). That should make things go back to green on
crake.

Thanks
--
Peter Geoghegan

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2021-03-11 03:39:13 pgsql: Improve comment for struct BufferDesc.
Previous Message Peter Geoghegan 2021-03-11 03:02:21 pgsql: Drop index behind pg_upgrade test issue.