Alfonso Escribano <alfonso.escribano@meteologica.com> writes:
> When client_connection_check_interval has any value, and
> log_lock_waits is enabled, the postgresql log displays a message
> about lock waits with the frequency of
> client_connection_check_interval.
When log_lock_waits is enabled, we'll print that "still waiting"
message anytime ProcSleep is awoken from a wait-for-lock sleep,
if it's already waited deadlock_timeout or longer. Normally there
isn't much that would awaken such a process other than being granted
the lock. But here, you've set client_connection_check_interval
so short that that interrupt happens repeatedly while waiting.
Why in the world would you want client_connection_check_interval
as short as 10 ms? Sane values would probably be more like 10 s.
regards, tom lane
