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

pgsql: Remove bogus comment from HeapTupleSatisfiesNow.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove bogus comment from HeapTupleSatisfiesNow.
Date: 2012-04-18 16:00:48
Message-ID: E1SKXJI-0001rM-VY@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Remove bogus comment from HeapTupleSatisfiesNow.

This has been wrong for a really long time.  We don't use two-phase
locking to protect against serialization anomalies.

Per discussion on pgsql-hackers about 2011-03-07; original report
by Dan Ports.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/293ec33c32e8e20fcb5859885a4b37ff6d855240

Modified Files
--------------
src/backend/utils/time/tqual.c |   10 ----------
1 files changed, 0 insertions(+), 10 deletions(-)

pgsql-committers by date

Next:From: Peter EisentrautDate: 2012-04-19 19:39:31
Subject: pgsql: Untabify DSSSL and XSL files and add to check-tabs target
Previous:From: Robert HaasDate: 2012-04-18 15:32:23
Subject: pgsql: Finish rename of FastPathStrongLocks toFastPathStrongRelationLo

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