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

pgsql-server: Now that xmax and cmin are distinct fields again, we

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql-server: Now that xmax and cmin are distinct fields again, we
Date: 2004-09-17 18:09:56
Message-ID: 20040917180956.0415D329D95@svr1.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Now that xmax and cmin are distinct fields again, we should zero xmax when
creating a new tuple.  This is just for debugging sanity, though, since
nothing should be paying any attention to xmax when the HEAP_XMAX_INVALID
bit is set.

Modified Files:
--------------
    pgsql-server/src/backend/access/heap:
        heapam.c (r1.175 -> r1.176)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/access/heap/heapam.c.diff?r1=1.175&r2=1.176)

pgsql-committers by date

Next:From: Tom LaneDate: 2004-09-17 18:28:54
Subject: pgsql-server: Hashed LEFT JOIN would miss outer tuples with no inner
Previous:From: Neil ConwayDate: 2004-09-17 02:06:41
Subject: pgsql-server: Hyperlink a reference to DROP CAST in the CREATE CAST

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