Re: Logging WAL when updating hintbit - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Logging WAL when updating hintbit
Date
Msg-id CA+TgmoZ82CDZZoSrEdQHsE4UtaX-ZwpNBXCVnTtPc2zpvK3i6A@mail.gmail.com
Whole thread Raw
In response to Logging WAL when updating hintbit  (Sawada Masahiko <sawada.mshk@gmail.com>)
Responses Re: Logging WAL when updating hintbit  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Thu, Nov 14, 2013 at 1:02 AM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:
> I attached patch adds new wal_level 'all'.
> If wal_level is set 'all', the server logs WAL not only when wal_level
> is set 'hot_standby' ,but also when updating hint bit.
> That is, we will be able to know all of the changed block number by
> reading the WALs.
> This wal_level is infrastructure for fast failback. (i.g., without fresh backup)
> It need to cooperate with pg_rewind.

This needs to be a separate parameter, not something that gets jammed
into wal_level.

I'm also not 100% sure we want it, but let's hear what others think.

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: better atomics - v0.2
Next
From: Andres Freund
Date:
Subject: Re: pre-commit triggers