Re: Is txid_status() actually safe? / What is 011_crash_recovery.pl testing? - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Is txid_status() actually safe? / What is 011_crash_recovery.pl testing?
Date
Msg-id CAMsr+YFZ1a_soUCx=x740JTznnQu=TwbVsp6x0MV8LhWTyzx-g@mail.gmail.com
Whole thread Raw
In response to Re: Is txid_status() actually safe? / What is 011_crash_recovery.pl testing?  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On Wed, 5 May 2021 at 23:15, Craig Ringer <craig@2ndquadrant.com> wrote:

> Which was fine as far as it went, but I failed to account for the xid
> assignment not necessarily being durable when the client calls
> txid_status().

Ahem, I meant "when the client calls txid_current()"

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 2ndQuadrant - PostgreSQL Solutions for the Enterprise

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Is txid_status() actually safe? / What is 011_crash_recovery.pl testing?
Next
From: "Joel Jacobson"
Date:
Subject: COPY table_name (single_column) FROM 'iso-8859-1.txt' DELIMITER E'\n'