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

Re: Unneccessary cmax in heap tuple ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: devik(at)cdi(dot)cz
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Unneccessary cmax in heap tuple ?
Date: 2000-10-25 18:04:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
devik(at)cdi(dot)cz writes:
> 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 ?

In situations like SQL function calls, it may be necessary to suspend
a table scan while we go off and do other commands, then come back and
resume the table scan.  So there can be multiple scans with different
command IDs in progress within a transaction.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2000-10-25 18:18:01
Subject: Re: --with-perl=/path/to/prefered/perl?
Previous:From: Lamar OwenDate: 2000-10-25 17:56:17
Subject: Re: [Fwd: [CORE SDI ADVISORY] MySQL weak authentication]

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