| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Sriram Dandapani <sdandapani(at)counterpane(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: [JDBC] number of transactions doubling |
| Date: | 2006-09-28 23:13:41 |
| Message-ID: | 451C5725.4070905@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-jdbc |
Sriram Dandapani wrote:
> Autocommit is set to off once a connection is obtained from the jboss
> pool. It is turned back on when it is closed (so that any idle
> transactions are committed).
Don't know what to suggest then -- if autocommit is off then the JDBC
driver should be sending BEGIN before the first query & COMMIT or
ROLLBACK when you explicitly delimit a transaction. There's nothing
special about batches.
You could set loglevel=2 as a JDBC URL parameter to see exactly what the
JDBC driver is sending, perhaps. Or turn on logging on the server side,
though I'm not sure at exactly which server version the logging of the
extended query protocol became useful.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-09-29 00:40:42 | Re: transaction id wraparound |
| Previous Message | Sriram Dandapani | 2006-09-28 23:03:38 | Re: [JDBC] number of transactions doubling |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-09-29 00:47:36 | Re: number of transactions doubling |
| Previous Message | Sriram Dandapani | 2006-09-28 23:03:38 | Re: [JDBC] number of transactions doubling |