[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] RI checks during UPDATEs
From:       "Simon Riggs" <simon () 2ndquadrant ! com>
Date:       2007-01-30 22:03:42
Message-ID: 1170194623.3681.272.camel () silverbirch ! site
[Download RAW message or body]

On Tue, 2007-01-30 at 15:24 -0500, Tom Lane wrote:
> "Simon Riggs" <simon@2ndquadrant.com> writes:
> > Any objections to implementing this?
> 
> Only that it was done a long time ago --- see
> RI_FKey_keyequal_upd_pk/fk.

OK, funny guy. :-)

Its not very well documented, is all I can say. The code comments
elsewhere in the file are very specific that the code applies to UPDATEs
as well as INSERTs, hence my confusion.

I'm relieved, actually, but still have a locking problem to resolve. 

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

[prev in list] [next in list] [prev in thread] [next in thread]