-----BEGIN PGP SIGNED MESSAGE-----
|> We have a database containing PostGIS MAP data, it is accessed
|> mainly via JDBC. There are multiple simultaneous read-only
|> connections taken from the JBoss connection pooling, and there
|> usually are no active writers. We use connection.setReadOnly(true).
|> Now my question is what is best performance-wise, if it does make
|> any difference at all:
|> Having autocommit on or off? (I presume "off")
|> Using commit or rollback?
|> Committing / rolling back occasionally (e. G. when returning the
|> connection to the pool) or not at all (until the pool closes the
| afaik, this should be completely neglectable.
| starting a transaction implies write access. if there is none, You do
| not need to think about transactions, because there are none.
| postgres needs to schedule the writing transactions with the reading
| ones, anyway.
| But I am not that performance profession anyway ;-)
Hello, Marcus, Nörder, list.
What about isolation? For several dependent calculations, MVCC doesn't
happen a bit with autocommit turned on, right?
~ Grega Bremec
~ gregab at p0f dot net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
-----END PGP SIGNATURE-----
In response to
pgsql-performance by date
|Next:||From: Nörder-Tuitje||Date: 2005-12-20 11:54:06|
|Subject: Re: Read only transactions - Commit or Rollback|
|Previous:||From: William Lai||Date: 2005-12-20 11:36:42|