Skip site navigation (1) Skip section navigation (2)

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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Robert Haas <rhaas(at)postgresql(dot)org>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Make the visibility map crash-safe.
Date: 2011-06-22 10:55:35
Message-ID: 4E01CA27.6010102@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
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.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-hackers by date

Next:From: Marti RaudseppDate: 2011-06-22 11:24:17
Subject: Re: Hugetables question
Previous:From: Florian PflugDate: 2011-06-22 10:47:42
Subject: Re: Another issue with invalid XML values

pgsql-committers by date

Next:From: Robert HaasDate: 2011-06-22 13:12:36
Subject: Re: [COMMITTERS] pgsql: Make the visibility map crash-safe.
Previous:From: Heikki LinnakangasDate: 2011-06-22 09:25:17
Subject: pgsql: Remove pointless const qualifiers from function arguments inthe

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group