xlog min recovery request is past current point -- is it real problem?

From: Sergey Burladyan <eshkinkot(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: xlog min recovery request is past current point -- is it real problem?
Date: 2014-09-07 22:21:39
Message-ID: 878ulvt6ks.fsf@seb.koffice.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello, All!

I get this messages from new standby:
2014-09-06 00:30:05 MSK pid=36409,user=,db=,host= LOG: restored log file "0000000A0001213C000000B1" from archive
2014-09-06 00:30:05 MSK pid=36447,user=,db=,host= WARNING: xlog min recovery request 12149/A5149BA0 is past current point 1213C/B1625590
2014-09-06 00:30:05 MSK pid=36447,user=,db=,host= CONTEXT: writing block 1 of relation base/16444/227548102_vm

Is my data broken and I will get wrong query results or it just some
warning without any problem for data?

PS:
PostgreSQL 9.2.6 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.7.2-5) 4.7.2, 64-bit
I promote standby to master, get backup from it and start new standby
from this backup. After all I get 43 messages like this in new standby log.

--
Sergey Burladyan

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Melvin Davidson 2014-09-08 00:17:52 Re: psql and tab-delimited output
Previous Message John R Pierce 2014-09-07 20:20:36 Re: Querying a time range across multiple partitions