aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeHashjoin.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2004-09-17 18:09:55 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2004-09-17 18:09:55 +0000
commit054b78ba38e7bd11db1725ede38675b5cfaebe0b (patch)
treeb0ad5d656e795365556d7896080f523c0f06d246 /src/backend/executor/nodeHashjoin.c
parent12ce26f8da1f309218073f5d505284829f29a02b (diff)
downloadpostgresql-054b78ba38e7bd11db1725ede38675b5cfaebe0b.tar.gz
postgresql-054b78ba38e7bd11db1725ede38675b5cfaebe0b.zip
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.
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions