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

From Tom Lane
Subject Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch
Date
Msg-id 24155.1171031308@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch  ("Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>)
List pgsql-hackers
"Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at> writes:
> 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.

No, it would not, because select for update would acquire exclusive lock
in the first place.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Variable length varlena headers redux
Next
From: "Merlin Moncure"
Date:
Subject: Re: [COMMITTERS] pgsql: Add lock matrix to documentation.