Re: Referential Integrity and SHARE locks - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Referential Integrity and SHARE locks
Date
Msg-id 200702052211.l15MBgS27896@momjian.us
Whole thread Raw
In response to Re: Referential Integrity and SHARE locks  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: Referential Integrity and SHARE locks  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Simon Riggs wrote:
> > It occurs to me that if we had visibility in unique indexes, this would
> > allow the index rows to be separately lockable to the main row. That's
> > exactly what we need here.
> 
> I've implemented a work-around using this principle, utilising RULEs and
> a duplicated PK column-only table. This still allows FK checks to work
> correctly, yet doesn't require the backend hack Csaba mentioned.
> 
> My feeling is that more work in this area is required, even if we can't
> yet agree a TODO item.

OK, please propose some wording so at least we can get agreement on
that.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: "Andrew Hammond"
Date:
Subject: Re: 10 weeks to feature freeze (Pending Work)
Next
From: Bruce Momjian
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add documentation for Windows on how to set an environment