On Wed, May 16, 2012 at 3:43 AM, Joshua Berkus <j...@agliodbs.com> wrote: > >> Before restarting it, you need to do pg_basebackup and make a base >> backup >> onto the standby again. Since you started the standby without >> recovery.conf, >> a series of WAL in the standby has gotten inconsistent with that in >> the master. >> So you need a fresh backup to restart the standby. > > You're not understanding the bug. The problem is that the standby came up > and reported that it was replicating OK, when clearly it wasn't.
> 8. Got this fatal error on the standby server: > > LOG: record with incorrect prev-link 0/70000B8 at 0/70000E0 > LOG: record with incorrect prev-link 0/70000B8 at 0/70000E0 > > ... this error message repeated every 5s. According to your first report, ISTM you got error messages. Regards, -- Fujii Masao -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
