Re: Guarenteeing complex referencial integrity through custom triggers - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Guarenteeing complex referencial integrity through custom triggers
Date
Msg-id 1175003097.3701.33.camel@localhost.localdomain
Whole thread Raw
In response to Guarenteeing complex referencial integrity through custom triggers  ("Joris Dobbelsteen" <Joris@familiedobbelsteen.nl>)
List pgsql-hackers
Ühel kenal päeval, E, 2007-03-26 kell 16:05, kirjutas Joris Dobbelsteen:

> Oracle has choosen to allow constraint enforcement by locking on the
> parent tuple. In contrast postgres has chosen (historically, see RI
> triggers) to fail on detecting conflicting newly inserted rows (the
> cross-check).

Could you give an example, where postgresql fails to detect conflicting
newly inserted rows ?

-- 
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia

Skype me:  callto:hkrosing
Get Skype for free:  http://www.skype.com




pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Concurrent connections in psql
Next
From: Tom Lane
Date:
Subject: Re: notification payloads