Skip site navigation (1) Skip section navigation (2)

Re: More FK patches

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: More FK patches
Date: 2001-11-22 02:28:44
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Was this resolved?


> This patch should help fix cases with two separate fk constraints
> in a row that happen to reference the same pk constraint with
> an on update cascade and similar cases.  It now should detect
> correctly that a pk row was added later after a delete or update
> on a no action deferred fk and not incorrect error as well
> as dropping a check on insert/update to the fk table if the
> row we're being referred to no longer is valid (I'm using
> HeapTupleSatisfiesItself because the comment implied it was
> what I was looking for and it appears to work :) ).
> I've got regression tests but I'm holding off on those until
> we decide whether or not we're dropping the triggered data change
> errors since a couple of the tests would hit that case and I'll
> either change them or drop them if we're not dropping the error.


[ Attachment, skipping... ]

> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-11-22 02:43:45
Subject: Re: rename index?
Previous:From: Bruce MomjianDate: 2001-11-22 02:28:02
Subject: Re: Foreign key referential actions

pgsql-patches by date

Next:From: Eiji TokuyaDate: 2001-11-22 03:44:46
Subject: Added Encoding
Previous:From: Tom LaneDate: 2001-11-21 22:15:04
Subject: Re: Rejection of the smallest int8

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group