From: | Net Llama! <netllama(at)linux-sxs(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Is autocommit=true bad? |
Date: | 2004-01-27 22:58:35 |
Message-ID: | Pine.LNX.4.55.0401271755170.14284@linux-sxs.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greetings,
I've been tasked with maintaining a postgresql-7.3.4 database that has a
J2EE app on the front end.
In the pgsql log I see thousands upon thousands of entries like these:
WARNING: COMMIT: no transaction in progress
Through a little googling, I've determined it means that the folks who
wrote the J2EE app have set autocommit=true. I'm not, by any means, a
java programmer, so I'm not sure if setting autocommit=true serves any
useful purpose, other than not having to add BEGIN and END statements to
your code.
At any rate, are there any negative consequences to setting setting
autocommit=true, such as performance hits (and the obvios filling up
diskspace because of the logging)?
thanks!
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J Friedman netllama(at)linux-sxs(dot)org
Linux Step-by-step & TyGeMo http://netllama.ipfox.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Satrapa | 2004-01-27 23:26:49 | Re: Is autocommit=true bad? |
Previous Message | Jerome Lyles | 2004-01-27 21:10:04 | Re: Where is initdb? |