| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RI checks during UPDATEs |
| Date: | 2007-01-30 22:03:42 |
| Message-ID: | 1170194623.3681.272.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2007-01-30 at 15:24 -0500, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-01-30 22:26:04 | parsenodes vs. primnodes |
| Previous Message | Simon Riggs | 2007-01-30 22:03:12 | Improving NOT IN |