pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Andres Freund <andres@anarazel.de>
Cc: Noah Misch <noah@leadboat.com>
Cc: David Rowley <dgrowleyml@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Intermittent buildfarm failures on wrasse
Date: Thu, 14 Apr 2022 22:40:51 -0400
Message-ID: <1576925.1649990451@sss.pgh.pa.us> (raw)
In-Reply-To: <CAH2-Wz=V=cd9wO+96_1htgjY6TrT6OF7BzR8W+vuPZMAwnUF4A@mail.gmail.com>
References: <1364997.1649893086@sss.pgh.pa.us>
	<CAH2-WzkUGqFNXhnFRbVG4xfTo3WpapcdRaH4hQSTrNvDgYvYoQ@mail.gmail.com>
	<1365924.1649893883@sss.pgh.pa.us>
	<CAH2-Wzn2Obp90oyZa5HN26rzG8ozzHM3dgkpLcsVzxTR+jK5NQ@mail.gmail.com>
	<1374062.1649896550@sss.pgh.pa.us>
	<20220414010505.s7z24jxrfsjbzz7l@alap3.anarazel.de>
	<1401379.1649899392@sss.pgh.pa.us>
	<20220414015112.yhruzx3dbjnz4pji@alap3.anarazel.de>
	<20220414025122.GA808845@rfd.leadboat.com>
	<1486022.1649952083@sss.pgh.pa.us>
	<20220414161850.ibqkevxcv6a7vdxg@alap3.anarazel.de>
	<1521388.1649953580@sss.pgh.pa.us>
	<1547912.1649971995@sss.pgh.pa.us>
	<CAH2-Wz=DHY2LV7=2aVd=qz6AbQhFK7KJRNL5ZwgB7dyno_gzdg@mail.gmail.com>
	<1553951.1649975018@sss.pgh.pa.us>
	<CAH2-WzngTjUk_65ESmrMf40WTqasrmWG0gpwnvcN+mXsoXT7qQ@mail.gmail.com>
	<CAH2-WznXXkkfE_y9ieaHkEQj31HeMAqJBtJPmDY+EpyVg1QywQ@mail.gmail.com>
	<1570894.1649986347@sss.pgh.pa.us>
	<CAH2-WznQ2j3n9QwfJ5Cp6RAPfbYCkh-Bgj2Vyk6Qh_HwFULRYw@mail.gmail.com>
	<1572437.1649987614@sss.pgh.pa.us>
	<CAH2-WznEA4EY! SdtPTaj_sTpSBvw8EtzxnFAEtEXQK2MYyCNq6A@mail.gmail.com>
	<1574961.1649989229@sss.pgh.pa.us>
	<CAH2-Wz=V=cd9wO+96_1htgjY6TrT6OF7BzR8W+vuPZMAwnUF4A@mail.gmail.com>

Peter Geoghegan <pg@bowt.ie> writes:
> Suppose that the bug was actually in 06f5295af6, "Add single-item
> cache when looking at topmost XID of a subtrans XID". Doesn't that fit
> your timeline just as well?

I'd dismissed that on the grounds that there are no subtrans XIDs
involved in tenk1's contents.  However, if that patch was faulty
enough, maybe it affected other cases besides the advertised one?
I've not read it.

			regards, tom lane





view thread (88+ messages)  latest in thread

Message-ID: <1576925.1649990451@sss.pgh.pa.us>
Permalink:  ../1576925.1649990451@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1576925.1649990451@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pg@bowt.ie, andres@anarazel.de, noah@leadboat.com, dgrowleyml@gmail.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: Intermittent buildfarm failures on wrasse
  In-Reply-To: <1576925.1649990451@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox