Re: improving foreign key locks - Mailing list pgsql-hackers

From Tom Lane
Subject Re: improving foreign key locks
Date
Msg-id 17049.1291220239@sss.pgh.pa.us
Whole thread Raw
In response to Re: improving foreign key locks  (Florian Pflug <fgp@phlo.org>)
Responses Re: improving foreign key locks  (Florian Pflug <fgp@phlo.org>)
List pgsql-hackers
Florian Pflug <fgp@phlo.org> writes:
> The validity wouldn't change, only the kind of lock taken. If all columns to be locked are part of some unique index,
we'drecord that fact in the locked tuple's infomask, and thus know that only a certain subset of columns are to be
preventedfrom being updated.
 

There's not enough space in the infomask to record which columns (or
which unique index) are involved.  And if you're talking about data that
could remain on disk long after the unique index is gone, that's not
going to be good enough.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: FK's to refer to rows in inheritance child
Next
From: Robert Haas
Date:
Subject: Re: crash-safe visibility map, take three