Tom Lane wrote:

> momjian@svr1.postgresql.org (Bruce Momjian) writes:
>>      someone asked me about the FK deadlock fix, mentioned in the 7.3.3
>>      release notes as 3rd change:
>>      http://www.postgresql.org/docs/current/static/release-7-3-3.html
>>      Actually, that fix was available with 7.4, not 7.3. Don't know if we can
>>      retroactively change the release-notes though.
>
> This is completely erroneous, please undo it.
>
> 2003-05-21 14:14  tgl
>
>       * src/: backend/utils/adt/ri_triggers.c,
>       test/regress/expected/foreign_key.out (REL7_3_STABLE): Back-patch
>       Jan's fix to avoid primary key lookup (and lock) if foreign key
>       does not change on UPDATE.

Oh ... didn't know that you did a backpatch. Sorry


Jan

HISTORY

@@ -462,8 +462,6 @@ Query Changes
        In prior releases, LIMIT/OFFSET could only use constants, not
        expressions.
      * Implement CREATE TABLE AS EXECUTE (Neil, Peter)
-     * Don't lock referenced row when "UPDATE" doesn't change foreign
-       key's value (Jan)
      _________________________________________________________________
    
 Object Manipulation Changes
@@ -940,6 +938,8 @@ Changes
      * Repair sometimes-incorrect computation of StartUpID after a crash
      * Avoid slowness with lots of deferred triggers in one transaction
        (Stephan)
+     * Don't lock referenced row when "UPDATE" doesn't change foreign
+       key's value (Jan)
      * Use "-fPIC" not "-fpic" on Sparc (Tom Callaway)
      * Repair lack of schema-awareness in contrib/reindexdb
      * Fix contrib/intarray error for zero-element result array (Teodor)