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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Improve XLOG_NO_TRAN related comments


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
  • Cc: pgsql-patches(at)postgresql(dot)org
  • Subject: Re: Improve XLOG_NO_TRAN related comments
  • Date: Mon, 26 Dec 2005 10:09:04 -0500
  • Message-id: <9457.1135609744@sss.pgh.pa.us> <text/plain>

Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu> writes:
> On Sat, 24 Dec 2005, Tom Lane wrote:
>> Removing these comments entirely, without changing the code they explain,
>> doesn't strike me as an improvement.

> I just checked if we can remove XLOG_NO_TRAN happily, and the conclusion
> is that it could bring some benefits (though not much) to our system. The
> key is the CheckpointStartLock lock.

Hm.  Perhaps we could keep the current behavior and re-document
XLOG_NO_TRAN as meaning that the xlog record does not involve the
insertion of our XID into permanent storage.

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group