From: Dimitar Georgievski <dgeorgievski@horizonk.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Update is very slow on a bigger table
Date: Fri, 16 Apr 2004 10:40:36 -0400
Message-ID: <1082126436.12136.46.camel@hklog> (raw)
In-Reply-To: <21949.1082069503@sss.pgh.pa.us>
References: <200404151507.RAA03297@rodos>
<1082063227.5415.217.camel@hklog>
<21949.1082069503@sss.pgh.pa.us>
Tom,
Yes. it looks like there was some locking condition in the database. in
the meantime it disappeared and the updates run quickly.
thanks for your help. this is the first time i'm working with PostgreSQL
and wasn't sure where to look for possible causes of the problem.
thanks,
dimitar
On Thu, 2004-04-15 at 18:51, Tom Lane wrote:
> 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: dgeorgievski@horizonk.com, tgl@sss.pgh.pa.us
Subject: Re: Update is very slow on a bigger table
In-Reply-To: <1082126436.12136.46.camel@hklog>
* 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