On Mon, Jul 02, 2001 at 09:40:25PM -0400, Tom Lane wrote:
> 4. It is considered OK to update tuple commit status bits (ie, OR the
> values HEAP_XMIN_COMMITTED, HEAP_XMIN_INVALID, HEAP_XMAX_COMMITTED, or
> HEAP_XMAX_INVALID into t_infomask) while holding only a shared lock and
> pin on a buffer. This is OK because another backend looking at the tuple
> at about the same time would OR the same bits into the field, so there
> is little or no risk of conflicting update; what's more, if there did
> manage to be a conflict it would merely mean that one bit-update would
> be lost and need to be done again later.
Without looking at the code, this seems mad. Are you sure?
In response to
pgsql-hackers by date
|Next:||From: Rod Taylor||Date: 2001-07-03 19:40:56|
|Subject: Re: Re: Backup and Recovery|
|Previous:||From: Tom Lane||Date: 2001-07-03 19:01:05|
|Subject: Re: stuck spin lock with many concurrent users |