I don't know: I'm not subscribed to the anno9unce list so I was not
aware 8.4 has now a production release.
In the past upgrading from 8.2 to 8.3 solved a big issues but at the
time the application is not in production.
So we are going to evaluate this option.
Anyway after reading the manual in th
Ivano Luberti writes:
> My problem is I know what query has failed , but I don't know the other
> one that caused the deadlock condition.
Ah. Is it practical for you to upgrade to PG 8.4? IIRC the deadlock
reporting code got improved in 8.4 to log all the queries involved.
Tom, thanks for your answer: the reason I failed to find
AccessExclusiveLock
is beacuse that string of character is never written in the manual while
AccessShareLock
is written as it is written above in the manual in the section about index
lockin.
Not knowing the manual in detail I didn't
Ivano Luberti writes:
> I'm trying to understand why I can have this kind or error (it is
> probably some programming mistake) but reading the PostgresSQL manual I
> cannot find any trace of AccessExclusiveLock , while I have found
> explanation of what AccessShareLock is.
> First question: is th
Hi all, I use PostgresSQL 8.3 through JDBC
Recently one transaction has failed with the following error message:
Detail: Process 10660 waits for AccessShareLock on relation 36036 of
database 34187; blocked by process 2212.
Process 2212 waits for AccessExclusiveLock on relation 36044 of database
34
