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

From: Daniel Cristian Cruz <danielcristian(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6226: Broken foreign key stored on database (parent deleted with children still readable, BUG#6225 Update)
Date: 2011-10-05 13:00:36
Message-ID: CACffM9EEBRqhTwW7Hcgadqjx4DLYmbOGcKEA+fMtqbYSdTzRyg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

2011/9/26 Alvaro Herrera <alvherre(at)commandprompt(dot)com>

>
> Please see if bug #6123 applies to this case.
> http://www.mail-archive.com/pgsql-hackers(at)postgresql(dot)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?

--
Daniel Cristian Cruz
クルズ クリスチアン ダニエル

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Holec 2011-10-05 13:37:54 Re: BUG #6233: pg_dump hangs with Access Violation C0000005
Previous Message Chethan HB 2011-10-05 11:12:26 Fwd: [BUGS] BUG #6240: About - postgreswdinit.sql