Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
Date
Msg-id A53779F4-748C-42C1-B968-8B3B321B95E4@yandex-team.ru
Whole thread
In response to Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row  (Zsolt Parragi <zsolt.parragi@percona.com>)
Responses Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
List pgsql-hackers
Hi Zsolt,

The snapshot change looks correct to me.

Two small points about the test:

The return value of poll_query_until() should be checked. On timeout it
returns false, so currently the test can continue without confirming
that the old worker has stopped.

ALTER DATABASE ... RESET does not change an existing worker's setting.
A worker starting between TRUNCATE and RESET can retain SERIALIZABLE
for the next test. I'd disable the subscription and wait for the worker
to stop, then truncate, reset the setting, and re-enable it.

Thank you!


Best regards, Andrey Borodin.




pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: Orphaned Files in PostgreSQL
Next
From: Japin Li
Date:
Subject: Re: Add counted_by attribute