Skip site navigation (1) Skip section navigation (2)

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

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Document the recently-understood hazard that a rollback can
Date: 2006-12-01 20:49:54
Message-ID: 20061201204954.2E37E9F9F0E@postgresql.org (view raw or flat)
Thread:
Lists: 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

Next:From: Tom LaneDate: 2006-12-01 20:50:00
Subject: pgsql: Document the recently-understood hazard that a rollback can
Previous:From: Tom LaneDate: 2006-12-01 19:55:29
Subject: pgsql: Make the bgwriter's error recovery path do smgrcloseall().

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group