X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 96020D1CCDA for ; Thu, 15 Apr 2004 19:51:39 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 44812-05 for ; Thu, 15 Apr 2004 19:51:43 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 66E17D1C9C8 for ; Thu, 15 Apr 2004 19:51:36 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i3FMpitM021950; Thu, 15 Apr 2004 18:51:44 -0400 (EDT) To: Dimitar Georgievski Cc: pgsql-sql@postgresql.org Subject: Re: Update is very slow on a bigger table In-reply-to: <1082063227.5415.217.camel@hklog> References: <200404151507.RAA03297@rodos> <1082063227.5415.217.camel@hklog> Comments: In-reply-to Dimitar Georgievski message dated "Thu, 15 Apr 2004 17:07:07 -0400" Date: Thu, 15 Apr 2004 18:51:43 -0400 Message-ID: <21949.1082069503@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/145 X-Sequence-Number: 17520 Dimitar Georgievski writes: > the process under which the update is running reports among the usual > process data "UPDATE waiting". I don't think the UPDATE is doing anything at all --- that ps output implies that it's waiting for some other backend to release an exclusive lock on the table, or an update lock on one of the rows to be updated. The pg_locks view might help you determine who's the culprit. regards, tom lane