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

Re: Re: Buffer access rules, and a probable bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
Cc: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: Buffer access rules, and a probable bug
Date: 2001-07-04 17:09:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> As for HeapTupleSatisfies() there seems to be another choise to
> let HeapTupleSatisfiesAny() be equivalent to HeapTupleSatisfiesNow()
> other than always returning true.

Wouldn't that break the other uses of SnapshotAny?  I'm not sure
it's what nbtree.c wants, either, because then the heap_getnext
call wouldn't return recently-dead tuples at all.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2001-07-04 17:12:16
Subject: Re: CREATE TABLE .. PRIMARY KEY quirk
Previous:From: Bruce MomjianDate: 2001-07-04 15:04:56
Subject: Re: Re: Backup and Recovery

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