| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | CM Team <cm(at)enterprisedb(dot)com> |
| Subject: | "ERROR: latch already owned" on gharial |
| Date: | 2022-05-25 00:45:21 |
| Message-ID: | CA+hUKGJ_0RGcr7oUNzcHdn7zHqHSB_wLSd3JyS2YC_DYB+-V=g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
A couple of recent isolation test failures reported $SUBJECT.
It could be a bug in recent-ish latch refactoring work, though I don't
know why it would show up twice just recently.
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).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shinoda, Noriyoshi (PN Japan FSIP) | 2022-05-25 01:08:12 | PG15 beta1 fix pg_stats_ext/pg_stats_ext_exprs view manual |
| Previous Message | Andres Freund | 2022-05-25 00:39:15 | Re: PG15 beta1 sort performance regression due to Generation context change |