From: | Alex Turner <armtuk(at)gmail(dot)com> |
---|---|
To: | Michael Fuhr <mike(at)fuhr(dot)org> |
Cc: | James Thompson <jamest(at)ajrs(dot)com>, PgSQL General List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Python Driver |
Date: | 2005-02-11 21:24:17 |
Message-ID: | 33c6269f05021113246bb02e0c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
pg_locks - awesome - I will check it out...
I think it's uncommitted transactions that are causing the problem.
The original code was written very transactionaly.
Alex Turner
netEconomist
On Fri, 11 Feb 2005 14:20:32 -0700, Michael Fuhr <mike(at)fuhr(dot)org> wrote:
> On Fri, Feb 11, 2005 at 04:05:03PM -0500, Alex Turner wrote:
> >
> > I am now having trouble with psycopg locking up my database somehow.
> > It's almost like there are outstanding locks on objects in the database
> > that are preventing other threads operating.
>
> Do you mean the Python script itself is locked up, or just that
> locks in the database are causing certain transactions to block?
> Have you looked at pg_locks? Are locks being held by idle uncommitted
> transactions?
>
> --
> Michael Fuhr
> http://www.fuhr.org/~mfuhr/
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Turner | 2005-02-11 21:26:04 | Re: Python Driver |
Previous Message | Michael Fuhr | 2005-02-11 21:20:32 | Re: Python Driver |