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

On Mon, Sep 8, 2014 at 7:21 AM, Sergey Burladyan <eshkinkot@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 "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?

This is similar to a bug report that has been sent a couple of months back:
/messages/by-id/1402313245515-5806482.post@n5.nabble.com

Here is explained why it may happen because of the visibility map code:
/messages/by-id/5395AB77.4080209@vmware.com
But as of now, there have been no fixes submitted for that. As that's
not the first bug report in the area, should we hasten a patch here? I
don't mind working on that if that's necessary. Just that I won't be
as fast as someone more familiar with the VM code :)

PS:
PostgreSQL 9.2.6 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.7.2-5) 4.7.2, 64-bit

You should update to latest 9.2 version, which is now 9.2.9.

Regards,
--
Michael

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general