Postgres Pro
Downloads
Home   >   mailing lists

too low NAPTIME_PER_CYCLE /too many wakeups in walreceiver.c - Mailing list pgsql-hackers

From Andres Freund
Subject too low NAPTIME_PER_CYCLE /too many wakeups in walreceiver.c
Date
Msg-id 201205301457.07444.andres@2ndquadrant.com
Whole thread Raw
Responses Re: too low NAPTIME_PER_CYCLE /too many wakeups in walreceiver.c
List pgsql-hackers
Tree view 
Hi,

Currently the walreceiver wakeups NAPTIME_PER_CYCLE=100 miliseconds in idle 
state. This is rather frequent. I don't really see any reason to do so.
A nice fix would be to latchify that with WaitLatchOrSocket + a SetLatch in 
the signal handler for shutdown but that seems to be too invasive at that 
point. So I suggest simply increasing NAPTIME_PER_CYCLE to 500 or 1000ms?

Andres

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Uh, I change my mind about commit_delay + commit_siblings (sort of)
Next
From: Merlin Moncure
Date:
Subject: Re: hash index concurrency