Oleg Bartunov <oleg@sai.msu.su> writes:
>> I'm not sure what would block a new backend for many minutes before
>> it did that, however. Can you attach to one of these processes with
>> a debugger and get a backtrace to show what it's doing?
> Below some output from ps and attached backtrace of one postmaster
> process.
Hmm, that backend is quite obviously done with initialization and
waiting for a client command. So why doesn't it show up as
"postgres ... idle" in ps?
I wonder whether we have the ps-info-setting operation in the wrong
place, ie at the bottom of the loop instead of the top, so that a
backend that hasn't yet received its first client command will never
have set the ps data. Will take a look.
regards, tom lane
