From: | devik(at)cdi(dot)cz |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Unneccessary cmax in heap tuple ? |
Date: | 2000-10-25 12:06:12 |
Message-ID: | 39F6CCB4.252706CC@cdi.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > 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.
Ahh I did not know that there is need to test tuple for
validity for some past cid. I thought that we only need
to know whether tuple has been updated by current cid
to ensure that it will not be scanned again in the same
cid... Where am I wrong ?
devik
From | Date | Subject | |
---|---|---|---|
Next Message | Kovacs Zoltan Sandor | 2000-10-25 12:10:07 | bug in views/aggregates |
Previous Message | andres mackiewicz | 2000-10-25 11:56:32 | DBD::Pg::st execute failed: ERROR |