Prev: : CRC32 is limiting at COPY/CTAS/INSERT... SELECT + speeding it up
Next: pgsql: Add current WAL end (as seen by walsender, ie, GetWriteRecPtr()
From: Fujii Masao on 7 Jun 2010 09:21
Hi,

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?

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: : CRC32 is limiting at COPY/CTAS/INSERT... SELECT + speeding it up
Next: pgsql: Add current WAL end (as seen by walsender, ie, GetWriteRecPtr()