| From: | Gokulakannan Somasundaram <gokul007(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: crash-safe visibility map, take four |
| Date: | 2011-03-24 04:56:44 |
| Message-ID: | AANLkTimboADH6m-c7uVpmi=BnXQYxp9ZySy4Nbko5Hkj@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Yeah. i looked at it. I don't think it addresses the problem raised here.
http://archives.postgresql.org/pgsql-hackers/2010-02/msg02097.php
<http://archives.postgresql.org/pgsql-hackers/2010-02/msg02097.php>Or may be
i am missing something.
Thanks.
On Wed, Mar 23, 2011 at 7:54 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Mar 23, 2011 at 2:29 AM, Gokulakannan Somasundaram
> <gokul007(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2011-03-24 11:02:49 | Re: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause, |
| Previous Message | Tom Lane | 2011-03-24 00:21:07 | Re: Query to generate CREATE INDEX statement from |