Re: [HACKERS] log messages for archive recovery progress

2012-01-12 Thread Robert Haas
On Wed, Jan 11, 2012 at 9:01 AM, Simon Riggs si...@2ndquadrant.com wrote: On Wed, Jan 11, 2012 at 1:54 PM, Satoshi Nagayasu sn...@uptime.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

Re: [HACKERS] log messages for archive recovery progress

2012-01-12 Thread Simon Riggs
On Thu, Jan 12, 2012 at 2:13 PM, Robert Haas robertmh...@gmail.com wrote: On Wed, Jan 11, 2012 at 9:01 AM, Simon Riggs si...@2ndquadrant.com wrote: On Wed, Jan 11, 2012 at 1:54 PM, Satoshi Nagayasu sn...@uptime.jp wrote: However, I'm a bit afraid that it will confuse DBA if we use restored

Re: [HACKERS] log messages for archive recovery progress

2012-01-12 Thread Robert Haas
On Thu, Jan 12, 2012 at 10:04 AM, Simon Riggs si...@2ndquadrant.com wrote: On Thu, Jan 12, 2012 at 2:13 PM, Robert Haas robertmh...@gmail.com wrote: On Wed, Jan 11, 2012 at 9:01 AM, Simon Riggs si...@2ndquadrant.com wrote: On Wed, Jan 11, 2012 at 1:54 PM, Satoshi Nagayasu sn...@uptime.jp wrote:

Re: [HACKERS] log messages for archive recovery progress

2012-01-12 Thread Satoshi Nagayasu
2012/01/13 0:13, Robert Haas wrote: On Thu, Jan 12, 2012 at 10:04 AM, Simon Riggssi...@2ndquadrant.com wrote: On Thu, Jan 12, 2012 at 2:13 PM, Robert Haasrobertmh...@gmail.com wrote: On Wed, Jan 11, 2012 at 9:01 AM, Simon Riggssi...@2ndquadrant.com wrote: On Wed, Jan 11, 2012 at 1:54 PM,

Re: [HACKERS] log messages for archive recovery progress

2012-01-12 Thread Fujii Masao
On Fri, Jan 13, 2012 at 12:58 AM, Satoshi Nagayasu sn...@uptime.jp wrote: Anyway, how about this one? If we have 47 in archive, and 48 in pg_xlog, (1) LOG: restored log file 00080047 from archive (2) LOG: replaying log file 00080047 (3) LOG: could not restore

Re: [HACKERS] log messages for archive recovery progress

2012-01-11 Thread Simon Riggs
2012/1/11 Euler Taveira de Oliveira eu...@timbira.com: On 08-01-2012 11:59, Satoshi Nagayasu / Uptime Technologies, LLC. wrote: [2011-12-08 15:14:36 JST] 16758: LOG:  restored log file 00080046 from archive [2011-12-08 15:14:36 JST] 16758: LOG:  recoverying

Re: [HACKERS] log messages for archive recovery progress

2012-01-11 Thread Satoshi Nagayasu
2012/01/11 19:56, Simon Riggs wrote: 2012/1/11 Euler Taveira de Oliveiraeu...@timbira.com: On 08-01-2012 11:59, Satoshi Nagayasu / Uptime Technologies, LLC. wrote: [2011-12-08 15:14:36 JST] 16758: LOG: restored log file 00080046 from archive [2011-12-08 15:14:36 JST] 16758:

Re: [HACKERS] log messages for archive recovery progress

2012-01-11 Thread Simon Riggs
On Wed, Jan 11, 2012 at 1:54 PM, Satoshi Nagayasu sn...@uptime.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

Re: [HACKERS] log messages for archive recovery progress

2012-01-10 Thread Euler Taveira de Oliveira
On 08-01-2012 11:59, Satoshi Nagayasu / Uptime Technologies, LLC. wrote: [2011-12-08 15:14:36 JST] 16758: LOG: restored log file 00080046 from archive [2011-12-08 15:14:36 JST] 16758: LOG: recoverying 00080046 [2011-12-08 15:14:36 JST] 16758: LOG: restored

[HACKERS] log messages for archive recovery progress

2012-01-08 Thread Satoshi Nagayasu / Uptime Technologies, LLC.
Hi, When I look into archive recovery deeply as DBA point of view, I found that it's difficult to know (1) when the recovery process switched reading WAL segments files from archive directory to pg_xlog directory, and (2) whether it succeeded applying the latest WAL segments in the pg_xlog