| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Gokulakannan Somasundaram <gokul007(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: crash-safe visibility map, take four |
| Date: | 2011-03-23 04:21:53 |
| Message-ID: | AANLkTikjnqmg87MJ+As_YNz+k42tkJ_nx6jN9r9aKsWq@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 22, 2011 at 11:59 PM, Gokulakannan Somasundaram
<gokul007(at)gmail(dot)com> wrote:
>> I took a crack at implementing the first approach described above,
>> which seems to be by far the simplest idea we've come up with to date.
>> Patch attached. It doesn't seem to be that complicated, which could
>> mean either that it's not that complicated or that I'm missing
>> something. Feel free to point and snicker in the latter case.
>>
> Hi,
> I suppose the problem is not with setting the bit, but resetting the
> bit. Has that been completed already?
> Thanks.
All operations that clear the bit area are already WAL-logged.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2011-03-23 05:48:14 | Re: pg_ctl restart - behaviour based on wrong instance |
| Previous Message | Gokulakannan Somasundaram | 2011-03-23 03:59:47 | Re: crash-safe visibility map, take four |