Request a Demo
Home   >   mailing lists

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

From Zsolt Parragi
Subject Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
Date
Msg-id CAN4CZFPz4ysPyo1ahD-5n0iyKxmuo2Wvn=PgEZTyW63_Tu7Eaw@mail.gmail.com
Whole thread
In response to Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row  (Dean Rasheed <dean.a.rasheed@gmail.com>)
Responses Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
List pgsql-hackers
Tree view 
Unfortunately I realized a bit late that v4 can cause a logical
replication crash because the apply worker doesn't have es_snapshot
set. This seems to be an oversight as CreateExecutorState documents
that the caller has to initialize es_snapshot, but
create_edata_for_relation never does so in worker.c

The attached patch sets it and adds a simple test case that shows the problem.
Attachment

pgsql-hackers by date:

Previous
From: Devrim Gündüz
Date:
Subject: [PATCH] Misleading error message for REPACK USING INDEX on shared catalogs
Next
From: Bharath Rupireddy
Date:
Subject: Re: Support for 8-byte TOAST values, round two