Horton

Re: 011_crash_recovery.pl intermittently fails

Thomas Munro <thomas.munro@gmail.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Geoghegan <pg@bowt.ie>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Craig Ringer <craig.ringer@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>
Date: 2021-03-08T01:03:08Z
Lists: pgsql-hackers 
On Mon, Mar 8, 2021 at 1:39 PM Kyotaro Horiguchi
<horikyota.ntt@gmail.com> wrote:
> At Fri, 05 Mar 2021 11:16:55 -0500, Tom Lane <tgl@sss.pgh.pa.us> wrote in
> > Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
> > But, of course, first we need a fix for the bug we now know exists.
> > Was anyone volunteering to make the patch?
>
> Thomas' proposal sounds reasonable. If he is not going to do that for
> now, I'm willing to work on that.

Thanks!  I'm afraid I wouldn't get around to it for a few weeks, so if
you have time, please do.  (I'm not sure if it's strictly necessary to
log *this* xid, if a higher xid has already been logged, considering
that the goal is just to avoid getting confused about an xid that is
recycled after crash recovery, but coordinating that might be more
complicated; I don't know.)

Commits

  1. Remove recovery test 011_crash_recovery.pl

  2. Add a txid_status function.