From: | sramirez <sramirez(at)vonage(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | warm-standby errors |
Date: | 2009-05-11 17:50:58 |
Message-ID: | 4A086582.5040302@vonage.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
We have a warm-standby of one of our databases, and by this I mean a
server in constant recovery mode applying logs being shipped from a
primary to the warm-standby. Recently we had to bounce the standby
instance and I saw this error in our logs:
2009-04-27 07:11:21.213 GMT,,,,8261,,,1, // LOG: database system was
interrupted while in recovery at log time 2009-04-27 06:55:08 GMT
2009-04-27 07:11:21.213 GMT,,,,8261,,,2, // HINT: If this has occurred
more than once some data may be corrupted and you may need to choose an
earlier recovery target.
2009-04-27 07:11:21.213 GMT,,,,8261,,,3, // LOG: starting archive recovery
the log message did not appear again until the instance was bounced
again. Short of copying the data files elsewhere and doing a row-level
comparison of the data, is there any way I can check to see if there is
actual corruption in the warm standby server? How can I prevent this
error from occurring ?
Thanks,
-Said
From | Date | Subject | |
---|---|---|---|
Next Message | BRUSSER Michael | 2009-05-11 18:10:26 | Build and install - how to avoid dependency on specific library version |
Previous Message | Tom Lane | 2009-05-11 17:00:01 | Re: Apparent race in information_schema.tables |