Re: [COMMITTERS] pgsql: Make the visibility map crash-safe. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [COMMITTERS] pgsql: Make the visibility map crash-safe.
Date
Msg-id BANLkTin44Ur6sWMYVsGoSz-w_yJbOf5Dkw@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Make the visibility map crash-safe.  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: [COMMITTERS] pgsql: Make the visibility map crash-safe.
List pgsql-hackers
On Wed, Jun 22, 2011 at 6:55 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> 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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Indication of db-shared tables
Next
From: Josh Kupershmidt
Date:
Subject: Re: smallserial / serial2