Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
| От | Álvaro Herrera |
|---|---|
| Тема | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY |
| Дата | |
| Msg-id | 202512080955.y7zzghv4vag2@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY (Mihail Nikalayeu <mihailnikalayeu@gmail.com>) |
| Ответы |
Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
|
| Список | pgsql-hackers |
On 2025-Dec-06, Mihail Nikalayeu wrote: > From my perspective, the correct solution - is to just remove the > error message, because it looks obsolete now. 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. 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? -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ <inflex> really, I see PHP as like a strange amalgamation of C, Perl, Shell <crab> inflex: you know that "amalgam" means "mixture with mercury", more or less, right? <crab> i.e., "deadly poison"
В списке pgsql-hackers по дате отправления: