"Brendan Hill" <brendanh@jims.net> writes:
> Using the Process Explorer tool, I've noticed that a child postgres.exe is
> chewing up 25% of the CPU usage each (we have two dual-core CPUs, presumably
> it's chewing up one core). Using SELECT * FROM pg_stat_activity, I located
> the process id (#3884), and it showed:
> <IDLE>
Hmph. When a new command is received, there's some amount of parsing
overhead that happens before it changes the status display to not-IDLE,
but it shouldn't be minutes' worth. Can you get a stack trace next time
that happens?
regards, tom lane