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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, 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 17:03:47
Message-ID: 2305303.1615482227@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> I now accept that the dump/reload hazards when upgrading to 14 are not
> acceptable. ISTM that adding back the reloption on master/Postgres 14
> (without doing anything with it) is the only way to fix everything.

Agreed, just keep it as a no-op. Not sure whether there should be
a documentation entry for it, but I bet we get questions if there
isn't.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2021-03-11 17:36:02 Re: pgsql: Don't consider newly inserted tuples in nbtree VACUUM.
Previous Message Peter Geoghegan 2021-03-11 16:55:52 Re: pgsql: Don't consider newly inserted tuples in nbtree VACUUM.