Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
| От | Mihail Nikalayeu |
|---|---|
| Тема | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY |
| Дата | |
| Msg-id | CADzfLwW2VkOrUujmWa2=5n_RY3onrFG4apqqyx8as1+F0USMMA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY (Álvaro Herrera <alvherre@kurilemu.de>) |
| Список | pgsql-hackers |
Hello, Álvaro! On Mon, Nov 24, 2025 at 6:49 PM Álvaro Herrera <alvherre@kurilemu.de> wrote: > This patch would bring the committed test file up to date with what you > last submitted. However, I didn't understand what is the problem with > the original formulation, and I haven't seen the test fail ... can you > explain? Yes, it looks strange - but it is the best option I have found so far. I've seen tests fail a few times in CI due to race. More details are available at [0] and particularly [1]. In a few words - it is an attempt to make sure the test goes to the wake-up backend only after it actually enters to wait mode. For that reason an additional 'notice' point is used by spec. I have proposed another possible solution for the [0] thread. Best regards, Mikhail. [0]: https://www.postgresql.org/message-id/flat/CADzfLwUc%3DjtSUEaQCtyt8zTeOJ-gHZ8%3Dw_KJsVjDOYSLqaY9Lg%40mail.gmail.com [1]: https://www.postgresql.org/message-id/flat/aREW7Qo0GqjfiHn7%40paquier.xyz#fde8593a6239a594724f8badd33f7266
В списке pgsql-hackers по дате отправления: