On Mon, 2010-04-05 at 19:29 +0100, Simon Riggs wrote:
> Looking through the code some more I note that their are two timing
> related parameters that are hardcoded into XLogPageRead(). At the very
> least such things should be #defines, though one of them was previously
> configurable using pg_standby, so I would like to see them both
> accessible to user tuning.
...the code says "we want to react quickly when the next WAL record
arrives" and then sleeps for 100ms.
> I was also surprised to note that the Startup process is not signaled by
> WALReceiver when new WAL is received, so it will continue sleeping even
> though it has work to do.
-- Simon Riggs www.2ndQuadrant.com
