Postgres Pro
Downloads
Home   >   mailing lists

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

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql-server: Now that xmax and cmin are distinct fields again, we
Date
Msg-id 20040917180956.0415D329D95@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
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:

Previous
From: neilc@svr1.postgresql.org (Neil Conway)
Date:
Subject: pgsql-server: Hyperlink a reference to DROP CAST in the CREATE CAST
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql-server: Hashed LEFT JOIN would miss outer tuples with no inner