Обсуждение: Fk fix for noaction update/delete

    This should fix a bug where a row that was updated or
deleted that had another row inserted/updated to its old
value during the same statement or other statements before the
integrity check for noaction would incorrectly error.  This
could happen in deferred constraints or due to triggers or
functions. It's effectively a reworking of the previous patch that
did a not exists to instead do a separate check.

Your patch has been added to the PostgreSQL unapplied patches list at:

    http://candle.pha.pa.us/cgi-bin/pgpatches

I will try to apply it within the next 48 hours.

---------------------------------------------------------------------------


Stephan Szabo wrote:
>
>     This should fix a bug where a row that was updated or
> deleted that had another row inserted/updated to its old
> value during the same statement or other statements before the
> integrity check for noaction would incorrectly error.  This
> could happen in deferred constraints or due to triggers or
> functions. It's effectively a reworking of the previous patch that
> did a not exists to instead do a separate check.
>

Content-Description:

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html

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

Patch applied.  Thanks.

---------------------------------------------------------------------------


Stephan Szabo wrote:
>
>     This should fix a bug where a row that was updated or
> deleted that had another row inserted/updated to its old
> value during the same statement or other statements before the
> integrity check for noaction would incorrectly error.  This
> could happen in deferred constraints or due to triggers or
> functions. It's effectively a reworking of the previous patch that
> did a not exists to instead do a separate check.
>

Content-Description:

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html

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