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

2014-09-07 Thread Sergey Burladyan
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 000A0001213C00B1 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

Re: [GENERAL] xlog min recovery request is past current point -- is it real problem?

2014-09-07 Thread Michael Paquier
On Mon, Sep 8, 2014 at 7:21 AM, Sergey Burladyan eshkin...@gmail.com wrote: 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 000A0001213C00B1 from archive 2014-09-06 00:30:05 MSK pid=36447,user=,db=,host=

Re: [GENERAL] xlog min recovery request ... is past current point ...

2013-08-04 Thread Michael Paquier
On Fri, Aug 2, 2013 at 11:33 PM, Alberto Bussolin alberto.busso...@edistar.com wrote: Hi, i was testing a point in time recovery on a postgres 9.1.9. When processing the xlog i found out these log messages (on postgres.log): postgres@postgres[[local]] FATAL: the database system is

[GENERAL] xlog min recovery request ... is past current point ...

2013-08-02 Thread Alberto Bussolin
Hi, i was testing a point in time recovery on a postgres 9.1.9. When processing the xlog i found out these log messages (on postgres.log): postgres@postgres[[local]] FATAL: the database system is starting up @[] LOG: restored log file 0002026B00D5 from archive @[] LOG: redo

[GENERAL] xlog min recovery request ... is past current point ...

2012-02-02 Thread Christophe Pettus
PostgreSQL 9.0.4: While bringing up a streaming replica, and while it is working its way through the WAL segments before connecting to the primary, I see a lot of messages of the form: 2012-02-01 21:26:13.978 PST,,,24448,,4f2a1e61.5f80,54,,2012-02-01 21:25:53 PST,1/0,0,LOG,0,restored log