| From: | Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Smolkin Grigory <smallkeen(at)gmail(dot)com> |
| Subject: | Re: race condition in pg_class |
| Date: | 2024-06-12 20:02:00 |
| Message-ID: | CANtu0ogYLrufbSWOLDjfcDNCU=R6i2SJCEG_Uejtezx_+2vHng@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello!
> Can you say more about the connection you see between $SUBJECT and that?
That
> looks like a valid report of an important bug, but I'm not following the
> potential relationship to $SUBJECT.
I was guided by the following logic:
* A pg_class race condition can cause table indexes to look stale.
* REINDEX updates indexes
* errors can be explained by different backends using different arbiter
indexes
> On your other thread, it would be useful to see stack traces from the
high-CPU
> processes once the live lock has ended all query completion.
I'll do.
Best regards,
Mikhail.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-06-12 20:02:44 | Re: Shouldn't jsonpath .string() Unwrap? |
| Previous Message | J F | 2024-06-12 19:51:48 | Re: Contributing test cases to improve coverage |