Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY

Hello!

On Sun, Nov 30, 2025 at 6:00 PM Alexander Lakhin <exclusion@gmail.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.

[0]:
https://www.postgresql.org/message-id/flat/CADzfLwUc%3DjtSUEaQCtyt8zTeOJ-gHZ8%3Dw_KJsVjDOYSLqaY9Lg%40mail.gmail.com