Re: log messages for archive recovery progress

From: Euler Taveira de Oliveira <euler(at)timbira(dot)com>
To: "Satoshi Nagayasu / Uptime Technologies, LLC(dot)" <snaga(at)uptime(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: log messages for archive recovery progress
Date: 2012-01-11 01:51:06
Message-ID: 4F0CEB0A.1020103@timbira.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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, Suporte 24x7 e Treinamento

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-01-11 02:04:46 Re: JSON for PG 9.2
Previous Message Joachim Wieland 2012-01-11 01:16:22 Re: Sending notifications from the master to the standby