On Mon, Jun 7, 2010 at 9:21 AM, Fujii Masao <masao.fu...@gmail.com> wrote: > When an error is found in the WAL streamed from the master, a warning > message is repeated without interval forever in the standby. This > consumes CPU load very much, and would interfere with read-only queries. > To fix this problem, we should add a sleep into emode_for_corrupt_record() > or somewhere? Or we should stop walreceiver and retry to read WAL from > pg_xlog or the archive?
I ran into this problem at one point, too, but was in the middle of trying to investigate a different bug and didn't have time to track down what was causing it. I think the basic question here is - if there's an error in the WAL, how do we expect to EVER recover? Even if we can read from the archive or pg_xlog, presumably it's the same WAL - why should we be any more successful the second time? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers