warm-standby errors
От | sramirez |
---|---|
Тема | warm-standby errors |
Дата | |
Msg-id | 4A086582.5040302@vonage.com обсуждение исходный текст |
Ответы |
Re: warm-standby errors
|
Список | 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
В списке pgsql-general по дате отправления: