Is autocommit=true bad?
От | Net Llama! |
---|---|
Тема | Is autocommit=true bad? |
Дата | |
Msg-id | Pine.LNX.4.55.0401271755170.14284@linux-sxs.org обсуждение исходный текст |
Ответы |
Re: Is autocommit=true bad?
Re: Is autocommit=true bad? |
Список | 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@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com
В списке pgsql-general по дате отправления: