From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dimitar Georgievski <dgeorgievski@horizonk.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Update is very slow on a bigger table
Date: Thu, 15 Apr 2004 18:51:43 -0400
Message-ID: <21949.1082069503@sss.pgh.pa.us> (raw)
In-Reply-To: <1082063227.5415.217.camel@hklog>
References: <200404151507.RAA03297@rodos>
<1082063227.5415.217.camel@hklog>
Dimitar Georgievski <dgeorgievski@horizonk.com> 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
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, dgeorgievski@horizonk.com
Subject: Re: Update is very slow on a bigger table
In-Reply-To: <21949.1082069503@sss.pgh.pa.us>
* 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