Re: Testing autovacuum wraparound (including failsafe)

From: Jacob Champion <jchampion(at)timescale(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Testing autovacuum wraparound (including failsafe)
Date: 2023-03-13 22:25:46
Message-ID: CAAWbhmh70j7FH3v6FyJYCxYwD7Sqv6m74BF9M-knMavoF+XVog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 11, 2023 at 8:47 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> I was joking. But I did have a real point: once we have tests for the
> xidStopLimit mechanism, why not take the opportunity to correct the
> long standing issue with the documentation advising the use of single
> user mode?

Does https://commitfest.postgresql.org/42/4128/ address that
independently enough?

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2023-03-13 22:32:03 Re: meson: Non-feature feature options
Previous Message Andres Freund 2023-03-13 22:20:08 Re: windows CI failing PMSignalState->PMChildFlags[slot] == PM_CHILD_ASSIGNED