Re: [HACKERS] Re: Referential Integrity In PostgreSQL - Mailing list pgsql-hackers

From Andreas Zeugswetter
Subject Re: [HACKERS] Re: Referential Integrity In PostgreSQL
Date
Msg-id 37E74EB9.44F9766E@telecom.at
Whole thread Raw
Responses Re: [HACKERS] Re: Referential Integrity In PostgreSQL
List pgsql-hackers
> Oh - well - vacuum shouldn't touch  relations  where
> deferred   triggers  are  outstanding.   Might  require  some
> special lock entry - Vadim?

All modified data will be in this same still open transaction.
Therefore no relevant data can be removed by vacuum anyway.

It is my understanding, that the RI check is performed on the newest 
available (committed) data (+ modified data from my own tx). 
E.g. a primary key that has been removed by another transaction after
my begin work will lead to an RI violation if referenced as foreign key.

Andreas


pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] Status on Jan Wieck
Next
From: Vince Vielhaber
Date:
Subject: Re: [HACKERS] Re: HISTORY for 6.5.2