Postgres Pro
Downloads
Home   >   mailing lists

Re: log messages for archive recovery progress - Mailing list pgsql-hackers

From Euler Taveira de Oliveira
Subject Re: log messages for archive recovery progress
Date
Msg-id 4F0CEB0A.1020103@timbira.com
Whole thread Raw
In response to log messages for archive recovery progress  ("Satoshi Nagayasu / Uptime Technologies, LLC." <snaga@uptime.jp>)
Responses Re: log messages for archive recovery progress  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Tree view 
On 08-01-2012 11:59, Satoshi Nagayasu / Uptime Technologies, LLC. wrote:
>> [2011-12-08 15:14:36 JST] 16758: LOG:  restored log file "000000080000000000000046" from archive
>> [2011-12-08 15:14:36 JST] 16758: LOG:  recoverying 000000080000000000000046
>> [2011-12-08 15:14:36 JST] 16758: LOG:  restored log file "000000080000000000000047" from archive
>> [2011-12-08 15:14:36 JST] 16758: LOG:  recoverying 000000080000000000000047
>> cp: cannot stat `/backups/archlog/000000080000000000000048': No such file or directory
>> [2011-12-08 15:14:37 JST] 16758: LOG:  could not restore file "000000080000000000000048" from archive
>> [2011-12-08 15:14:37 JST] 16758: LOG:  attempting to look into pg_xlog
>> [2011-12-08 15:14:37 JST] 16758: LOG:  recoverying 000000080000000000000048
> 
What about just 'restored log file "000000080000000000000048" from pg_xlog'
instead of the last two messages? If you can't read from pg_xlog emit 'could
not restore file "000000080000000000000048" from pg_xlog'.


--   Euler Taveira de Oliveira - Timbira       http://www.timbira.com.br/  PostgreSQL: Consultoria, Desenvolvimento,
Suporte24x7 e Treinamento

pgsql-hackers by date:

Previous
From: Joachim Wieland
Date:
Subject: Re: Sending notifications from the master to the standby
Next
From: Robert Haas
Date:
Subject: Re: JSON for PG 9.2