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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, 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 19:13:19
Message-ID: CA+TgmobkCExv7Zo+pArRCsJ16hYVJJB_VuZKwvk1cCP=rS1Qbw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Mar 11, 2021 at 1:57 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> I think that this commit has some issues that need more thoughts.

My biggest issue with this commit is that I can't understand from the
commit message why it's a bug fix that deserves to be back-patched. To
be honest, I can't even really understand whether it's a good idea in
master.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2021-03-11 19:22:04 Re: pgsql: Don't consider newly inserted tuples in nbtree VACUUM.
Previous Message Robert Haas 2021-03-11 19:02:10 pgsql: Refactor and generalize the ParallelSlot machinery.