> On further thought, btbuild is not that badly broken at the moment,
> because CREATE INDEX acquires ShareLock on the relation, so
> there can be no concurrent writers at the page level. Still, it
> seems like it'd be a good idea to do "LockBuffer(buffer,
> here, and probably also to invoke HeapTupleSatisfiesNow() via the
> HeapTupleSatisfies() macro so that infomask update is checked for.
> Vadim, what do you think?
Looks like there is no drawback in locking buffer so let's lock it.
pgsql-hackers by date
|Next:||From: Joe Brenner||Date: 2001-07-03 17:44:04|
|Subject: [OT] Any major users of postgresql? |
|Previous:||From: Tom Lane||Date: 2001-07-03 17:34:08|
|Subject: Re: selecting from cursor |