From: | Jaime Casanova <systemguards(at)gmail(dot)com> |
---|---|
To: | Frank Miles <fpm(at)u(dot)washington(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: What causes lock? |
Date: | 2005-08-04 22:58:04 |
Message-ID: | c2d9e70e050804155874a88d40@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/4/05, Frank Miles <fpm(at)u(dot)washington(dot)edu> wrote:
> Hi everyone...
>
> I have a python-based application which provides a user interface
> to a Postgresql database. The latest version of the application suddenly
> lost the inability to insert new data in some of the tables. The SQL
> statement(s) used still work if manually typed in psql, but it appears as
> though there are some locks that are persisting and prevent inserts and
> updates when the application is still running. Examining pg_locks shows a
> number of locks (almost all of mode 'AccessShareLock'). Other inserts
> and updates (to other tables) still work. The database logs (default
> noise level setting) don't show any errors.
>
AccessShareLocks are safe, it's the type of lock a SELECT does.
The fact that you can execute the statements in psql show that the
problem is not about locking...
Are you sure there isn't a problem on your client side?
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-08-04 23:14:30 | Re: What causes lock? |
Previous Message | Brent Wood | 2005-08-04 22:56:26 | Re: dbf to pgsql |