From: Markus Schaber <schabi@logix-tt.com>
To: PostgreSQL Performance List <pgsql-performance@postgresql.org>
Subject: Read only transactions - Commit or Rollback
Date: Tue, 20 Dec 2005 11:40:53 +0100
Message-ID: <43A7DFB5.3030408@logix-tt.com> (raw)
Hello,
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
connection)?
Thanks,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: schabi@logix-tt.com
Subject: Re: Read only transactions - Commit or Rollback
In-Reply-To: <43A7DFB5.3030408@logix-tt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox