From: | Dimitar Georgievski <dgeorgievski(at)horizonk(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Update is very slow on a bigger table |
Date: | 2004-04-16 14:40:36 |
Message-ID: | 1082126436.12136.46.camel@hklog |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)horizonk(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Cornelius Grotjahn | 2004-04-16 17:43:31 | What is the best way of writing update rule on view with joined tables? |
Previous Message | Charity M | 2004-04-16 12:32:57 | Re: Database triggers |