JDBC autocommit versus own commits performance

Поиск

Список

Период

Сортировка

От	David Wall
Тема	JDBC autocommit versus own commits performance
Дата	12 марта 2001 г. 19:24:53
Msg-id	001e01c0ab53$1c6e4d80$5a2b7ad8@expertrade.com обсуждение исходный текст
Список	pgsql-interfaces

Дерево обсуждения

I'm using Postgresql 7.1beta4 with JDBC, and I was wondering if I should go to the trouble of modifying my connection pool to manage two pools, once with setAutoCommit(false) and the other with setAutoCommit(true).

As it is, I turne off auto commit since in my transaction processing, I need to control the commit/rollback.

But, there are also a lot of cases where I'm doing a simple query and I don't need transaction isolation, per se. Is the performance better if I use auto-commit than if I SELECT and do a commit() myself? And is there any benefit to doing a rollback on a select instead of a commit, since nothing changed?

Would there be a benefit with auto commit off if I had to do several different SELECTs, since I'd only have to do one commit at the end instead of the autocommits after each step?

Thanks,

David

В списке pgsql-interfaces по дате отправления:

Вход в личный кабинет

Восстановление пароля

Подтверждение аккаунта

Изменение пароля

JDBC autocommit versus own commits performance