Обсуждение: ON DELETE CASCADE with multiple paths in PostgreSQL 9.x
Hello! 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? May be there are some settings/workarounds that could help in this situation without patching PostgreSQL server? -- Anton Dedov Senior Software Developer Parallels Automation Parallels
Anton Dedov <adedov@parallels.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
I though that following message provided evidence for bug: http://archives.= postgresql.org/pgsql-bugs/2007-05/msg00135.php -- Anton Dedov ________________________________________ From: Tom Lane [tgl@sss.pgh.pa.us] Sent: Tuesday, June 07, 2011 7:33 PM To: Anton Dedov Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] ON DELETE CASCADE with multiple paths in PostgreSQL 9.x Anton Dedov <adedov@parallels.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