Skip site navigation (1) Skip section navigation (2)

xlog min recovery request ... is past current point ...

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: xlog min recovery request ... is past current point ...
Date: 2012-02-03 16:32:25
Message-ID: CFCD6054-BA8E-48A1-A414-8EB351C59F93@thebuild.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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,00000,"restored log file ""0000000100000DB400000065"" from archive",,,,,,,,,""
2012-02-01 21:26:14.032 PST,,,24448,,4f2a1e61.5f80,55,,2012-02-01 21:25:53 PST,1/0,0,WARNING,01000,"xlog min recovery request DB5/42E15098 is past current point DB4/657FA490",,,,,"writing block 5 of relation base/155650/156470_vm
xlog redo insert: rel 1663/155650/1658867; tid 9640/53",,,,""
2012-02-01 21:26:14.526 PST,,,24448,,4f2a1e61.5f80,56,,2012-02-01 21:25:53 PST,1/0,0,LOG,00000,"restored log file ""0000000100000DB400000066"" from archive",,,,,,,,,""

All of these are on _vm relations.  The recovery completed successfully and the secondary connected to the primary without issue, so: Are these messages something to be concerned over?

--
-- Christophe Pettus
  xof(at)thebuild(dot)com


Responses

pgsql-hackers by date

Next:From: Michael MeskesDate: 2012-02-03 16:48:08
Subject: Re: ecpglib use PQconnectdbParams
Previous:From: Marti RaudseppDate: 2012-02-03 16:28:06
Subject: Re: Caching for stable expressions with constant arguments v6

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group