| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Michail Nikolaev <michail(dot)nikolaev(at)gmail(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 19:48:57 |
| Message-ID: | 20240612194857.1c.nmisch@google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 12, 2024 at 03:02:43PM +0200, Michail Nikolaev wrote:
> I am not sure, but I think that issue may be related to the issue described
> in
> https://www.postgresql.org/message-id/CANtu0ojXmqjmEzp-%3DaJSxjsdE76iAsRgHBoK0QtYHimb_mEfsg%40mail.gmail.com
>
> It looks like REINDEX CONCURRENTLY could interfere with ON CONFLICT UPDATE
> in some strange way.
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.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J F | 2024-06-12 19:51:48 | Re: Contributing test cases to improve coverage |
| Previous Message | Tom Lane | 2024-06-12 19:45:19 | Re: Improve the granularity of PQsocketPoll's timeout parameter? |