Skip site navigation (1) Skip section navigation (2)

Re: improving foreign key locks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Florian Pflug <fgp(at)phlo(dot)org>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: improving foreign key locks
Date: 2010-12-01 16:17:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Florian Pflug <fgp(at)phlo(dot)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'd record that fact in the locked tuple's infomask, and thus know that only a certain subset of columns are to be prevented from 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

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2010-12-01 16:25:36
Subject: Re: crash-safe visibility map, take three
Previous:From: Simon RiggsDate: 2010-12-01 16:16:37
Subject: Re: FK's to refer to rows in inheritance child

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group