Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
| От | Mihail Nikalayeu |
|---|---|
| Тема | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY |
| Дата | |
| Msg-id | CADzfLwWznDA_iCmjkiW0jcPstV=pgE6yhV3zpg9xG2Ykpe=U0Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
|
| Список | pgsql-hackers |
Hello, Andres! On Sun, Dec 14, 2025 at 4:19 PM Andres Freund <andres@anarazel.de> wrote: > There are a *lot* of these right now. CI on master currently has a failure > rate of 14 failures / 50 runs on the postgres/postgres repo. All of the > failures are due to this issue from what I can tell. That means there are a > lot of false failures for cfbot. Oh, that's sad :( > Could we perhaps disable this test until it's been rewritten to be stable? Of course, if you can do it yourself, feel free to do so for all test from the set: index-concurrently-upsert index-concurrently-upsert-predicate reindex-concurrently-upsert reindex-concurrently-upsert-on-constraint reindex-concurrently-upsert-partitioned You may even remove them for now - I plan to rewrite them using TAP infrastructure, because "endless fight" from [0] seems to be true now. [0]: https://www.postgresql.org/message-id/flat/CADzfLwUhvaEsPbYaT3Z5cMO779JruDqBbE5nijeaBcXiNPoCYw%40mail.gmail.com#97598dff6875c788765e62b18bc3ee63
В списке pgsql-hackers по дате отправления: