On Tue, May 21, 2013 at 11:59 AM, Benedikt Grundmann <bgrundm...@janestreet.com> wrote: > We are seeing these errors on a regular basis on the testing box now. We > have even changed the backup script to > shutdown the hot standby, take lvm snapshot, restart the hot standby, rsync > the lvm snapshot. It still happens. > > We have never seen this before we introduced the hot standby. So we will > now revert to taking the backups from lvm snapshots on the production > database. If you have ideas of what else we should try / what information > we can give you to debug this let us know and we will try to so. > > Until then we will sadly operate on the assumption that the combination of > hot standby and "frozen snapshot" backup of it is not production ready.
I'm pretty suspicious that your backup procedure is messed up in some way. The fact that you got invalid page headers is really difficult to attribute to a PostgreSQL bug. A number of the other messages that you have posted also tend to indicate either corruption, or that WAL replay has stopped early. It would be interesting to see the logs from when the clone was first started up, juxtaposed against the later WAL flush error messages. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
