Postgres Pro
Downloads
Home   >   mailing lists

Re: crash-safe visibility map, take four - Mailing list pgsql-hackers

From Gokulakannan Somasundaram
Subject Re: crash-safe visibility map, take four
Date
Msg-id AANLkTimboADH6m-c7uVpmi=BnXQYxp9ZySy4Nbko5Hkj@mail.gmail.com
Whole thread Raw
In response to Re: crash-safe visibility map, take four  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: crash-safe visibility map, take four
List pgsql-hackers
Tree view
Yeah. i looked at it. I don't think it addresses the problem raised here.


Or may be i am missing something.

Thanks.

On Wed, Mar 23, 2011 at 7:54 PM, Robert Haas <robertmhaas@gmail.com> wrote:
On Wed, Mar 23, 2011 at 2:29 AM, Gokulakannan Somasundaram
<gokul007@gmail.com> wrote:
>> All operations that clear the bit area are already WAL-logged.
>>
> Is it the case with visibility map also?
> Thanks.

Yes.  Look at the comment that the patch removes.  That describes the
problem being fixed.

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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Query to generate CREATE INDEX statement from
Next
From: Fujii Masao
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,