Excerpts from Daniel Cristian Cruz's message of mié oct 05 10:00:36 -0300 2011: > 2011/9/26 Alvaro Herrera <alvhe...@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?
Well, some people say it's a bug, others say it's not; and even if it is, changing it means backwards incompatible behavior, so *if* it is patched, it will only change the behavior on a future release, not whatever you're using. > Where can I change it to avoid it? I don't know enough about the problem to help you there, sorry. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
