On 14/09/10 16:02, Fujii Masao wrote:
> Hi,
>
> In 9.1dev, wal_sender_delay in *milliseconds* is given
> to WaitLatchOrSocket as *microseconds* timeout. This is
> obviously wrong. The attached patch fixes this problem.
Thanks, fixed.
I was just wondering earlier this morning why walsender process was
consuming so much CPU while there was nothing happening. Should've rang
the bells..
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com