Re: slow DELETE on 12 M row table

On Fri, Jun 26, 2009 at 9:34 AM, Janet Jacobsen<jsjacobsen@lbl.gov> wrote:

> I assume that killing the user's process released the lock on the
> table.  This user has only SELECT privileges.  Under what
> conditions would a SELECT lock a table.  The user connects
> to the database via a (Python?) script that runs on another
> machine.  Would this way of connecting to the database result
> in a lock?

Was this process 'idle in transaction' perhaps? Does this Python
script use any ORM, like SQLAlchemy? If not, which library does it use
to connect? If it's psycopg2, which isolation level (autocommit, read
committed, serializable) is set?

Regards,
Marcin