X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D998A9FA159 for ; Tue, 9 May 2006 21:51:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 80930-09 for ; Tue, 9 May 2006 21:51:49 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.197]) by postgresql.org (Postfix) with ESMTP id C27319F9DCD for ; Tue, 9 May 2006 21:51:49 -0300 (ADT) Received: by nz-out-0102.google.com with SMTP id k1so1556690nzf for ; Tue, 09 May 2006 17:51:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Z3ON1YGedpE9WtAb4NrQ5B9piYXo+yhjZpRVwu3J7KMw8/QoUxtMZQW3W8r6JOqAh64+Snz3flCbzZmz352GKPS6dVD/L5F4rfY2B1vTX3OA1jEcpz0Whim/YnFP6jTcTOkU0vCOYwVIiaM9P6tmD/K254UjQN7FubqOzPs/0BU= Received: by 10.36.251.60 with SMTP id y60mr5840364nzh; Tue, 09 May 2006 17:51:45 -0700 (PDT) Received: from ?10.1.1.21? ( [203.217.18.65]) by mx.gmail.com with ESMTP id 7sm7178882nzn.2006.05.09.17.51.44; Tue, 09 May 2006 17:51:45 -0700 (PDT) Message-ID: <4461391D.2000800@gmail.com> Date: Wed, 10 May 2006 10:51:41 +1000 From: Chris User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Craig A. James" CC: pgsql-performance@postgresql.org Subject: Re: Postgres gets stuck References: <446135F9.1060608@modgraph-usa.com> In-Reply-To: <446135F9.1060608@modgraph-usa.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/200 X-Sequence-Number: 18987 > 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/