Re: Finding out on exactly what I am stuck - Mailing list pgsql-admin

From Kevin Grittner
Subject Re: Finding out on exactly what I am stuck
Date
Msg-id 49DF0683.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Re: Finding out on exactly what I am stuck  (Péter Kovács <maxottovonstirlitz@gmail.com>)
Responses Re: Finding out on exactly what I am stuck  (Péter Kovács <maxottovonstirlitz@gmail.com>)
List pgsql-admin
Péter Kovács <maxottovonstirlitz@gmail.com> wrote:
> It appears nobody is waiting for a lock (all current locks are
> granted):

Then I would run the UPDATE on another connection with EXPLAIN in
front of it.  That would show you the plan it will use, which might
give a clue why it is running so long.

Also, a connection which is "idle in transaction" will prevent normal
maintenance and may lead to table bloat which can kill performance.
It could be that your problem is there.  You might want to check how
big your database is (using du or something similar), and make sure
that the size seems reasonable.

I hope this helps.

-Kevin

pgsql-admin by date:

Previous
From: Kevin Bailey
Date:
Subject: backing and restoring whole database server - how does this script look
Next
From: P Kapat
Date:
Subject: Re: backing and restoring whole database server - how does this script look