Re: "ERROR: latch already owned" on gharial
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, CM Team <cm@enterprisedb.com>
Date: 2022-05-25T01:24:39Z
Lists: pgsql-hackers
Hi, On 2022-05-25 12:45:21 +1200, Thomas Munro wrote: > A couple of recent isolation test failures reported $SUBJECT. Was that just on gharial? > It could be a bug in recent-ish latch refactoring work, though I don't > know why it would show up twice just recently. Yea, that's weird. > Just BTW, that animal has shown signs of a flaky toolchain before[1]. > I know we have quite a lot of museum exhibits in the 'farm, in terms > of hardare, OS, and tool chain. In some cases, they're probably just > forgotten/not on anyone's upgrade radar. If they've shown signs of > misbehaving, maybe it's time to figure out if they can be upgraded? > For example, it'd be nice to be able to rule out problems in GCC 4.6.0 > (that's like running PostgreSQL 9.1.0, in terms of vintage, > unsupported status, and long list of missing bugfixes from the time > when it was supported). Yea. gcc 4.6.0 is pretty ridiculous - the only thing we gain by testing with a .0 compiler of that vintage is pain. Could it be upgraded? TBH, I think we should just desupport HPUX. It's makework to support it at this point. 11.31 v3 is about to be old enough to drink in quite a few countries... Greetings, Andres Freund
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add debugging help in OwnLatch().
- 12e28aac8e8e 15.0 landed
-
Add barriers to the latch code.
- 14e8803f101a 9.5.0 cited