Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch
Date
Msg-id E1539E0ED7043848906A8FF995BDA57901C13306@m0143.s-mxs.net
Whole thread Raw
In response to Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> As for what I think we *should* do near-term, I'm pretty strongly
> tempted to suggest that we just throw an error if a subtransaction
tries
> to upgrade an upper transaction's shared lock to exclusive.

So when a RI check locks a parent, you would not be able to update the
parent
in a later subtrans.
I can imagine, that the error would be a problem in a select for update
loop,
because there you usually want to update the row.

Andreas


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [PATCHES] [pgsql-patches] Phantom Command IDs,updated patch
Next
From: Peter Eisentraut
Date:
Subject: Re: [COMMITTERS] pgsql: Add lock matrix to documentation.