Обсуждение: ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query

Поиск
Список
Период
Сортировка

ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query

От
"David Wall"
Дата:
When using the latest 7.1 release with JDBC, if I do two "group deletes" (each transaction deletes about 10 messages, which probably translates to deleting 30-40 rows from 3-4 tables on the same connection), I am getting the following errors in my server log.
 
ERROR:  SET TRANSACTION ISOLATION LEVEL must be called before any query
NOTICE:  current transaction is aborted, queries ignored until end of transaction block
I have to kill my client before I can do anything more.
 
David

Re: ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query

От
"David Wall"
Дата:
> ERROR:  SET TRANSACTION ISOLATION LEVEL must be called before any query
> NOTICE:  current transaction is aborted, queries ignored until end of
transaction block

Oops.  Sorry.  It looks like it was a bug in the connection pool class that
I've been magically using for a couple of years now.  Apparently the usage
just never ran into the problem, or there's a difference in the Tomcat
servlet engine I'm using that was driving the database.  The code was
reusing the connection for all pool calls from the same thread.

David