Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
| От | Mihail Nikalayeu |
|---|---|
| Тема | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY |
| Дата | |
| Msg-id | CADzfLwXDS7QfJ6=vbWBQ2w-pATwR+3x60iRPXfj7eGWd21FemQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY (Álvaro Herrera <alvherre@kurilemu.de>) |
| Ответы |
Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
|
| Список | pgsql-hackers |
Hello, Álvaro! On Mon, Dec 8, 2025 at 10:58 AM Álvaro Herrera <alvherre@kurilemu.de> wrote: > Rereading this -- did you mean to propose that a possible fix was to > remove the "invalid arbiter index list" error? I had understood > something different. Yes, it was the initial idea. > Your idea downthread of changing the way that check works (so that we > don't throw an error in this case, but we continue to double-check that > the arbiter list is sensible) sounds reasonable to me. Do you want to > propose a specific check for it? I think the next logic is correct: * for each IS indisvalid arbiter in the parent table we should have AT LEAST ONE compatible indisvalid pair in the partition (we may have multiple or a few more ready-only) * for each NOT indisvalid arbiter in parent - nothing is expected from partition I'll try to create a patch with such later. Best regards, Mikhail.
В списке pgsql-hackers по дате отправления: