Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Simple query showing 270 hours of CPU time
- From: PFC <lists(at)peufeu(dot)com>
- To: "Dan Harris" <fbsd(at)drivefaster(dot)net>, "PostgreSQL Performance" <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: Simple query showing 270 hours of CPU time
- Date: Fri, 20 Jul 2007 18:55:02 +0200
Today, I looked at 'top' on my PG server and saw a pid that reported 270 hours of CPU time. Considering this is a very simple query, I was surprised to say the least. I was about to just kill the pid, but I figured I'd try and see exactly what it was stuck doing for so long.
If you are using connection pooling, or if your client keeps the connections for a long time, this backend could be very old... With PHP's persistent connections, for instance, backends restart when you restart the webserver, which isn't usually very often.
- References:
- Simple query showing 270 hours of CPU time
- From: Dan Harris
- Simple query showing 270 hours of CPU time
- Prev by Date: Re: Simple query showing 270 hours of CPU time
- Next by Date: Re: 8.2 -> 8.3 performance numbers
- Previous by thread: Re: Simple query showing 270 hours of CPU time
- Next by thread: Simple select hangs while CPU close to 100%
- Indexes: