On Wed, Jun 22, 2011 at 6:55 AM, Heikki Linnakangas
> On 22.06.2011 06:05, Robert Haas wrote:
>> Second, when inserting, updating, or deleting
>> a tuple, we can no longer get away with clearing the visibility map
>> bit after releasing the lock on the corresponding heap page, because
>> an intervening crash might leave the visibility map bit set and the
>> page-level bit clear.
> heap_update seems to still do that.
Aw, crap. I'll take another look.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Josh Kupershmidt||Date: 2011-06-22 13:14:47|
|Subject: Re: smallserial / serial2|
|Previous:||From: Bruce Momjian||Date: 2011-06-22 13:10:02|
|Subject: Re: Indication of db-shared tables|
pgsql-committers by date
|Next:||From: Robert Haas||Date: 2011-06-22 13:43:48|
|Subject: pgsql: Don't select log_cnt in sequence regression tests.|
|Previous:||From: Heikki Linnakangas||Date: 2011-06-22 10:55:35|
|Subject: Re: [COMMITTERS] pgsql: Make the visibility map crash-safe.|