Re: ON DELETE CASCADE with multiple paths in PostgreSQL 9.x

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Anton Dedov <adedov(at)parallels(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: ON DELETE CASCADE with multiple paths in PostgreSQL 9.x
Date: 2011-06-07 15:33:29
Message-ID: 14092.1307460809@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Anton Dedov <adedov(at)parallels(dot)com> writes:
> We are using patched version of PostgreSQL 8.1 in order to work-around
> bug described in
> http://archives.postgresql.org/pgsql-bugs/2007-05/msg00130.php. Now, we
> are going to upgrade to 9.0 and it also would be great to get rid of
> patch as it makes keeping database engine current too expensive task.
> I've checked 9.0 and it seems that undesirable behavior is still there.
> Is there any plans to fix it in future releases?

It wasn't a bug then, and it isn't a bug now. There is no guarantee of
the order in which FK constraints will be checked.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-06-07 15:41:22 Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view
Previous Message Robert Haas 2011-06-07 15:28:40 Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view