Re: recovering from "found xmin ... from before relfrozenxid ..."

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: recovering from "found xmin ... from before relfrozenxid ..."
Date: 2020-07-29 22:29:52
Message-ID: CA+hUKGKDD_KBrOPXFppxO5B48Q96CAVAuk3wHxXnZbXT7qrHiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 30, 2020 at 1:36 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Jul 29, 2020 at 3:23 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> > On Tue, Jul 14, 2020 at 9:12 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > > A number of EDB customers have had this error crop on their tables for
> > > reasons that we have usually not been able to determine. In many
> >
> > <long-shot>Do you happen to know if they ever used the
> > snapshot-too-old feature?</long-shot>
>
> I don't have any reason to believe that they did. Why?

Nothing specific, I was just contemplating the problems with that
feature and the patches[1] proposed so far to fix some of them, and
what types of corruption might be possible due to that stuff, and it
occurred to me to ask if you'd thought about that in connection to
these reports.

[1] https://www.postgresql.org/message-id/flat/CA%2BTgmoY%3Daqf0zjTD%2B3dUWYkgMiNDegDLFjo%2B6ze%3DWtpik%2B3XqA%40mail.gmail.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2020-07-29 22:34:22 Re: PG 13 release notes, first draft
Previous Message Daniel Gustafsson 2020-07-29 21:34:07 Re: Ought to use heap_multi_insert() for pg_attribute/depend insertions?