From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Satoshi Nagayasu <snaga(at)uptime(dot)jp> |
Cc: | Euler Taveira de Oliveira <euler(at)timbira(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: log messages for archive recovery progress |
Date: | 2012-01-11 14:01:46 |
Message-ID: | CA+U5nML5Qyy3rjFe-OXLrAB2oAz_X2-gEx2Djj6wsHYOc0oMkA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 11, 2012 at 1:54 PM, Satoshi Nagayasu <snaga(at)uptime(dot)jp> wrote:
> However, I'm a bit afraid that it will confuse DBA if we use
> "restored" under the pg_xlog replay context, because we have
> already used "restored" that means a WAL file as successfully
> "copied" (not "replayed") from archive directory into pg_xlog
> directory under the archive recovery context.
>
> So, to determine the status of copying WAL files from
> archive directory, I think we can use "restored", or
> "could not restore" on failure.
>
> And to determine the status of replaying WAL files
> in pg_xlog directory (even if a WAL is copied from archive),
> we have to use "recover" or "replay".
Agreed. I can change "restored" to "using", so we have two message types
LOG: restored log file "000000080000000000000047" from archive
LOG: using pre-existing log file "000000080000000000000047" from pg_xlog
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-01-11 14:04:25 | Re: JSON for PG 9.2 |
Previous Message | Satoshi Nagayasu | 2012-01-11 13:54:23 | Re: log messages for archive recovery progress |