pgsql: Document the recently-understood hazard that a rollback can - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Document the recently-understood hazard that a rollback can
Date
Msg-id 20061201204954.2E37E9F9F0E@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Document the recently-understood hazard that a rollback can release row-level
locks that logically should not be released, because when a subtransaction
overwrites XMAX all knowledge of the previous lock state is lost.  It seems
unlikely that we will be able to fix this before 8.3...

Modified Files:
--------------
    pgsql/doc/src/sgml/ref:
        select.sgml (r1.93 -> r1.94)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/select.sgml.diff?r1=1.93&r2=1.94)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Make the bgwriter's error recovery path do smgrcloseall().
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Document the recently-understood hazard that a rollback can