From: PFC <lists@peufeu.com>
To: Dan Harris <fbsd@drivefaster.net>
To: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Simple query showing 270 hours of CPU time
Date: Fri, 20 Jul 2007 18:55:02 +0200
Message-ID: <op.tvrvx0sjcigqcu@apollo13> (raw)
In-Reply-To: <46A0D836.5090806@drivefaster.net>
References: <46A0D836.5090806@drivefaster.net>
> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: lists@peufeu.com, fbsd@drivefaster.net
Subject: Re: Simple query showing 270 hours of CPU time
In-Reply-To: <op.tvrvx0sjcigqcu@apollo13>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox