Re: Is txid_status() actually safe? / What is 011_crash_recovery.pl testing?

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Is txid_status() actually safe? / What is 011_crash_recovery.pl testing?
Date: 2021-05-05 15:17:13
Message-ID: CAMsr+YFZ1a_soUCx=x740JTznnQu=TwbVsp6x0MV8LhWTyzx-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 5 May 2021 at 23:15, Craig Ringer <craig(at)2ndquadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2021-05-05 15:30:30 COPY table_name (single_column) FROM 'unknown.txt' DELIMITER E'\n'
Previous Message Craig Ringer 2021-05-05 15:15:53 Re: Is txid_status() actually safe? / What is 011_crash_recovery.pl testing?