pgsql: Improve behavior of log_lock_waits patch. - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Improve behavior of log_lock_waits patch.
Date
Msg-id 20070828032344.39A6E754201@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Improve behavior of log_lock_waits patch.  Ensure that something gets logged
even if the "deadlock detected" ERROR message is suppressed by an exception
catcher.  Be clearer about the event sequence when a soft deadlock is fixed:
the fixing process might or might not still have to wait, so log that
separately.  Fix race condition when someone releases us from the lock partway
through printing all this junk --- we'd not get confused about our state, but
the log message sequence could have been misleading, ie, a "still waiting"
message with no subsequent "acquired" message.  Greg Stark and Tom Lane.

Modified Files:
--------------
    pgsql/src/backend/storage/lmgr:
        proc.c (r1.191 -> r1.192)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/proc.c?r1=1.191&r2=1.192)

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Mention configurations early in text search documentation to
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Please ignore.