Thread: Backpatch FK changes to 7.3 and 7.2?

Followup-To: pgsql-hackers@postgresql.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@Yahoo.com #

Jan Wieck <JanWieck@Yahoo.com> writes:
> 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.

I would vote against it --- it seems a nontrivial change to be putting
into stable branches, especially without any testing ;-)

            regards, tom lane