Re: PITR promote bug: Checkpointer writes to older timeline
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>,
Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
masao.fujii@oss.nttdata.com, soumyadeep2007@gmail.com,
hlinnaka@iki.fi,
pgsql-hackers@postgresql.org, jyih@vmware.com, kyeap@vmware.com
Date: 2021-06-27T19:13:20Z
Lists: pgsql-hackers
Attachments
- transaction-ordering-assertion-failures.txt (text/plain)
I wrote: > Buildfarm member hornet just reported a failure in this test: > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hornet&dt=2021-06-27%2013%3A40%3A57 > It's not clear whether this is a problem with the test case or an > actual server bug, but I'm leaning to the latter theory. My gut > feel is it's some problem in the "snapshot scalability" work. It > doesn't look the same as the known open issue, but maybe related? Hmm, the plot thickens. I scraped the buildfarm logs for similar-looking assertion failures back to last August, when the snapshot scalability patches went in. The first such failure is not until 2021-03-24 (see attachment), and they all look to be triggered by 023_pitr_prepared_xact.pl. It sure looks like recovering a prepared transaction creates a transient state in which a new backend will compute a broken snapshot. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix timeline assignment in checkpoints with 2PC transactions
- 1ec7162a8d34 10.17 landed
- f1d550f188e2 11.12 landed
- 4b1dd9b1ea75 12.7 landed
- 6e5ce888ad1e 13.3 landed
- 595b9cba2ab0 14.0 landed