Re: [BUGS] ON DELETE SET NULL clauses do error when more than two columns are referenced to one table

2007-08-13 Thread Tom Lane
Heikki Linnakangas <[EMAIL PROTECTED]> writes: > I'm not sure what to do about this. We could change the order the > triggers are fired to breadth-first. If all the setnull triggers were > executed first, there would be no problem. But that seems like a pretty > big change, and I'm afraid it might

Re: [BUGS] failed to re-find parent key in "..." for deletion target page

2007-08-13 Thread Brian Hirt
Unfortunately, I wasn't able to get Tom the requested files. On Aug 10, 2007, at 8:11 AM, Heikki Linnakangas wrote: Any news on this? Tom Lane wrote: Brian Hirt <[EMAIL PROTECTED]> writes: basement_dev=# VACUUM FULL developer_name; ERROR: failed to re-find parent key in "developer_name_deve

Re: [BUGS] ON DELETE SET NULL clauses do error when more than two columns are referenced to one table

2007-08-13 Thread Gregory Stark
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes: > I'm not sure what to do about this. We could change the order the > triggers are fired to breadth-first. If all the setnull triggers were > executed first, there would be no problem. But that seems like a pretty > big change, and I'm afraid it mig

Re: [BUGS] ON DELETE SET NULL clauses do error when more than two columns are referenced to one table

2007-08-13 Thread Heikki Linnakangas
Pavel Stehule wrote: > One question on www.abclinuxu.cz signalise bug in PostgreSQL RI > implementation. Detected on 8.0.x and verified on 8.3. What seems to happen under the hood is: 1. The row in users is deleted 2. The setnull trigger on owner is fired, which executes "UPDATE ONLY users SET ow