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:50:06
Message-ID: 20061201205006.D8CB69FA12B@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
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...

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
pgsql/doc/src/sgml/ref:
select.sgml (r1.80.4.2 -> r1.80.4.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/select.sgml.diff?r1=1.80.4.2&r2=1.80.4.3)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2006-12-01 21:17:52 pgsql: Some more supported-platforms updates: buildfarm hare is alive
Previous Message Tom Lane 2006-12-01 20:50:00 pgsql: Document the recently-understood hazard that a rollback can