From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | PostgreSQL general <pgsql-general(at)postgresql(dot)org>, PostgreSQL development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Backpatch FK changes to 7.3 and 7.2? |
Date: | 2003-04-07 20:51:57 |
Message-ID: | 3E91E4ED.8AA47836@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Followup-To: pgsql-hackers(at)postgresql(dot)org
The changes I committed to address most of the FK deadlock problems
reported can easily be applied to the 7.3 and 7.2 source trees as well.
Except for a slight change in the text of the error message that gets
thrown "if one tries to delete a referenced PK for which a FK with ON
DELETE SET DEFAULT exists" (it's a rare case, believe me), this patch
would qualify for backpatching. The unnecessary FOR UPDATE lock of
referenced rows could be counted as a bug.
Opinions?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2003-04-07 21:04:42 | Re: Consecutive queries |
Previous Message | Jan Wieck | 2003-04-07 20:51:33 | FK deadlock problem addressed |
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Wampler | 2003-04-07 20:57:54 | Re: No merge sort? |
Previous Message | Jan Wieck | 2003-04-07 20:51:33 | FK deadlock problem addressed |