Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> Dead(HEAP_XMAX_COMMITTED || HEAP_XMIN_INVALID) tuples never
> revive. Live (not dead) tuples never die in Share Lock mode.
Hmm ... so you're relying on the ShareLock to ensure that the state of
the tuple can't change between when heap_fetch checks it and when
nbtree looks at it.
Okay, but put in some comments documenting what this stuff is doing
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2001-07-05 13:57:35|
|Subject: Re: AW: Strange query execution time |
|Previous:||From: Tom Lane||Date: 2001-07-05 13:47:03|
|Subject: Re: stuck spin lock with many concurrent users |