xlog min recovery request ... is past current point ...
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 "000000020000026B000000D5" from archive
@[] LOG: redo starts at 26B/D50049F0
@[] WARNING: xlog min recovery request 26B/EB529C40 is past current point 26B/D5758198
@[] CONTEXT: writing block 0 of relation base/2831418/257279491_vm xlog redo insert: rel 1663/1425752962/2572579716; tid 3235/118
The restore procedure completed correctly and all the data was restored.
May i ignore this warning or is it something i didn't realise?
Alberto Bussolin
Import Notes
Reply to msg id not found: 1404958524.5002.1375451844644.JavaMail.root@mailserver.edistar.com
On Fri, Aug 2, 2013 at 11:33 PM, Alberto Bussolin <
alberto.bussolin@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 starting up
@[] LOG: restored log file "000000020000026B000000D5" from archive
@[] LOG: redo starts at 26B/D50049F0
@[] WARNING: xlog min recovery request 26B/EB529C40 is past current
point 26B/D5758198
@[] CONTEXT: writing block 0 of relation base/2831418/257279491_vm xlog
redo insert: rel 1663/1425752962/2572579716; tid 3235/118The restore procedure completed correctly and all the data was restored.
May i ignore this warning or is it something i didn't realise?
Similar problem on the VM relations has been reported before:
/messages/by-id/4F53C562.5060402@enterprisedb.com
This is harmless, and by looking at the git log history this warning has
not been fixed as it is not that straight-forward.
Regards,
--
Michael