From: 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 13:03:15 +0100
Message-ID: <43A7F303.8040804@logix-tt.com> (raw)
In-Reply-To: <16F953410A0F1346848DCB476A989CFE01D6AF@swtexchange2.technology.de>
References: <16F953410A0F1346848DCB476A989CFE01D6AF@swtexchange2.technology.de>
Hi, Marcus,
Nörder-Tuitje wrote:
> 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.
Hmm, I always thought that the transaction will be opened at the first
statement, because there _could_ be a parallel writing transaction
started later.
> postgres needs to schedule the writing transactions with the reading
> ones, anyway.
As I said, there usually are no writing transactions on the same database.
Btw, there's another setting that might make a difference:
Having ACID-Level SERIALIZABLE or READ COMMITED?
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: <43A7F303.8040804@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