From: Chris <dmagick@gmail.com>
To: Craig A. James <cjames@modgraph-usa.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres gets stuck
Date: Wed, 10 May 2006 10:51:41 +1000
Message-ID: <4461391D.2000800@gmail.com> (raw)
In-Reply-To: <446135F9.1060608@modgraph-usa.com>
References: <446135F9.1060608@modgraph-usa.com>
> This is a deadly bug, because our web site goes dead when this happens,
> and it requires an administrator to log in and kill the stuck postgres
> process then restart Postgres. We've installed failover system so that
> the web site is diverted to a backup server, but since this has happened
> twice in one week, we're worried.
>
> Any ideas?
Sounds like a deadlock issue.
Do you have query logging turned on?
Also, edit your postgresql.conf file and add (or uncomment):
stats_command_string = true
and restart postgresql.
then you'll be able to:
select * from pg_stat_activity;
to see what queries postgres is running and that might give you some clues.
--
Postgresql & php tutorials
http://www.designmagick.com/
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: dmagick@gmail.com, cjames@modgraph-usa.com
Subject: Re: Postgres gets stuck
In-Reply-To: <4461391D.2000800@gmail.com>
* 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