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 99FDE9DC822 for ; Tue, 20 Dec 2005 06:55:25 -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 53915-01 for ; Tue, 20 Dec 2005 06:55:27 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by postgresql.org (Postfix) with ESMTP id F27EF9DC82A for ; Tue, 20 Dec 2005 06:55:22 -0400 (AST) Received: from [80.142.122.154] (helo=swtexchange2.technology.de) by mrelayeu.kundenserver.de (node=mrelayeu5) with ESMTP (Nemesis), id 0ML25U-1Eof9P3Cvu-0008Fw; Tue, 20 Dec 2005 11:55:24 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: Read only transactions - Commit or Rollback X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 Date: Tue, 20 Dec 2005 11:55:23 +0100 Message-ID: <16F953410A0F1346848DCB476A989CFE01D6AF@swtexchange2.technology.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PERFORM] Read only transactions - Commit or Rollback Thread-Index: AcYFUoaXI+mBaL21RFKFfjxKOlBi3QAAQnnA From: =?iso-8859-1?Q?N=F6rder-Tuitje=2C_Marcus?= To: "Markus Schaber" , "PostgreSQL Performance List" X-Provags-ID: kundenserver.de abuse@kundenserver.de login:24478085a861b01e05bdc3b8f80dc176 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.129 required=5 tests=[AWL=0.129] X-Spam-Score: 0.129 X-Spam-Level: X-Archive-Number: 200512/479 X-Sequence-Number: 16300 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 ;-) regards, Marcus -----Urspr=FCngliche Nachricht----- Von: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org]Im Auftrag von Markus Schaber Gesendet: Dienstag, 20. Dezember 2005 11:41 An: PostgreSQL Performance List Betreff: [PERFORM] Read only transactions - Commit or Rollback 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 --=20 Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in EU! www.ffii.org = www.nosoftwarepatents.org ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend