pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Nörder-Tuitje, Marcus <noerder-tuitje@technology.de>
To: Markus Schaber <schabi@logix-tt.com>
To: PostgreSQL Performance List <pgsql-performance@postgresql.org>
Subject: Re: Read only transactions - Commit or Rollback
Date: Tue, 20 Dec 2005 11:55:23 +0100
Message-ID: <16F953410A0F1346848DCB476A989CFE01D6AF@swtexchange2.technology.de> (raw)

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üngliche 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

-- 
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





view thread (13+ messages)  latest in thread

Message-ID: <16F953410A0F1346848DCB476A989CFE01D6AF@swtexchange2.technology.de>
Permalink:  ../16F953410A0F1346848DCB476A989CFE01D6AF@swtexchange2.technology.de/
Also on:    postgresql.org/message-id/16F953410A0F1346848DCB476A989CFE01D6AF@swtexchange2.technology.de

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: noerder-tuitje@technology.de, schabi@logix-tt.com
  Subject: Re: Read only transactions - Commit or Rollback
  In-Reply-To: <16F953410A0F1346848DCB476A989CFE01D6AF@swtexchange2.technology.de>
  References: <16F953410A0F1346848DCB476A989CFE01D6AF@swtexchange2.technology.de>

* 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