Re: Overhauling "Routine Vacuuming" docs, particularly its handling of freezing

From: Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Overhauling "Routine Vacuuming" docs, particularly its handling of freezing
Date: 2023-05-01 19:03:38
Message-ID: CAOtHd0BKAnSJpT_acdgWTOM-5nHC2RvacOi+a99iCXPm+-r7dg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 1, 2023, 18:08 Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> I am saying that, while wraparound is perhaps not a perfect term
> for what's happening, it is not, in my opinion, a bad term either.

I don't want to put words into Peter's mouth, but I think that he's arguing
that the term "wraparound" suggests that there is something special about
the transition between xid 2^32 and xid 0 (or, well, 3). There isn't.
There's only something special about the transition, as your current xid
advances, between the xid that's half the xid space ahead of your current
xid and the xid that's half the xid space behind the current xid, if the
latter is not frozen. I don't think that's what most users think of when
they hear "wraparound".

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2023-05-01 19:35:29 Re: Overhauling "Routine Vacuuming" docs, particularly its handling of freezing
Previous Message Eric Ridge 2023-05-01 18:25:24 Re: [PATCH] Support % wildcard in extension upgrade filenames