Re: BUG #6226: Broken foreign key stored on database (parent deleted with children still readable, BUG#6225 Update) - Mailing list pgsql-bugs

2011/9/26 Alvaro Herrera <alvherre@commandprompt.com>

>
> Please see if bug #6123 applies to this case.
> http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg181541.html


I guess, yes, it's related, because we had a trigger that deletes a row,
while other foreign key constraint is updating the row setting null.

But the thread is almost a book, and I am confused. It's a bug or do I need
to change my schema? Where can I change it to avoid it?

--=20
Daniel Cristian Cruz
=E3=82=AF=E3=83=AB=E3=82=BA =E3=82=AF=E3=83=AA=E3=82=B9=E3=83=81=E3=82=A2=
=E3=83=B3 =E3=83=80=E3=83=8B=E3=82=A8=E3=83=AB