| From: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY |
| Date: | 2025-11-30 17:26:18 |
| Message-ID: | CADzfLwUhvaEsPbYaT3Z5cMO779JruDqBbE5nijeaBcXiNPoCYw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello!
On Sun, Nov 30, 2025 at 6:00 PM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> s1: NOTICE: notice triggered for injection point pre-invalidate-catalog-snapshot-end
> +s1: NOTICE: notice triggered for injection point pre-invalidate-catalog-snapshot-end
> step s1_start_upsert: <... completed>
> step s2_start_upsert: <... completed>
> step s3_start_create_index: <... completed>
Oh, I'm afraid it may become an endless fight....
I think it is better to implement something in isolationtester to
natively support the case from [0] (in such case we don't need NOTICE
on .pre-invalidate-catalog-snapshot-end).
Best regards,
Mikhail.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2025-11-30 18:09:15 | Re: meson and check-tests |
| Previous Message | Alexander Lakhin | 2025-11-30 17:00:01 | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY |