X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id A19389DC82A
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Tue, 20 Dec 2005 06:41:52 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 50955-04
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Tue, 20 Dec 2005 06:41:53 -0400 (AST)
Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159])
	by postgresql.org (Postfix) with ESMTP id 2EDB89DC81A
	for <pgsql-performance@postgresql.org>;
	Tue, 20 Dec 2005 06:41:49 -0400 (AST)
Received: from mail.logix-tt.com (serval.logix-tt.com [213.239.221.42])
	by svr4.postgresql.org (Postfix) with ESMTP id CB6D45AF190
	for <pgsql-performance@postgresql.org>;
	Tue, 20 Dec 2005 10:41:50 +0000 (GMT)
Received: from kingfisher.intern.logix-tt.com (K8ed2.k.pppool.de
	[85.75.142.210])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.logix-tt.com (Postfix) with ESMTP id 4825F24400F;
	Tue, 20 Dec 2005 11:48:00 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id CD541D6CAE;
	Tue, 20 Dec 2005 11:40:53 +0100 (CET)
Message-ID: <43A7DFB5.3030408@logix-tt.com>
Date: Tue, 20 Dec 2005 11:40:53 +0100
From: Markus Schaber <schabi@logix-tt.com>
Organization: Logical Tracking and Tracing International AG, Switzerland
User-Agent: Debian Thunderbird 1.0.7 (X11/20051017)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: PostgreSQL Performance List <pgsql-performance@postgresql.org>
Subject: Read only transactions - Commit or Rollback
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0 required=5 tests=[none]
X-Spam-Score: 0
X-Spam-Level: 
X-Archive-Number: 200512/478
X-Sequence-Number: 16299

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