From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Logging WAL when updating hintbit |
Date: | 2013-11-19 16:42:06 |
Message-ID: | CA+TgmoZ82CDZZoSrEdQHsE4UtaX-ZwpNBXCVnTtPc2zpvK3i6A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 14, 2013 at 1:02 AM, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-11-19 16:42:35 | Re: pre-commit triggers |
Previous Message | Andres Freund | 2013-11-19 16:38:33 | Re: better atomics - v0.2 |