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

Re: Unneccessary cmax in heap tuple ?

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: devik(at)cdi(dot)cz
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Unneccessary cmax in heap tuple ?
Date: 2000-10-25 09:49:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

devik(at)cdi(dot)cz wrote:

> Hello,
> Why is there cmax in tuple ? cxxx is used to determine
> if tuple was inserted/deleted by current command or
> past command. Because one command can't both insert
> and delete the same tuple, only something like "cupd"
> might be needed and flag which tells you whether cupd
> is time of insert or delete. This saves 4byte from
> header ..

If a tuple was inserted and updated in current transaction,
how could we judge if the tuple was valid for a given
ScanCommandId  ?
However there could be other improvements.

Hiroshi Inoue

In response to


pgsql-hackers by date

Next:From: Holger KlawitterDate: 2000-10-25 09:54:17
Subject: Re: latest version?
Previous:From: Larry RosenmanDate: 2000-10-25 09:45:10
Subject: --with-perl=/path/to/prefered/perl?

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