From: Andreas Seltenreich <andreas+pg@gate450.dyndns.org>
To: Markus Schaber <schabi@logix-tt.com>
Cc: PostgreSQL Performance List <pgsql-performance@postgresql.org>
Subject: Re: Read only transactions - Commit or Rollback
Date: Tue, 20 Dec 2005 13:27:05 +0100
Message-ID: <87mziwj6na.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <43A7F303.8040804@logix-tt.com>
References: <16F953410A0F1346848DCB476A989CFE01D6AF@swtexchange2.technology.de>
<43A7F303.8040804@logix-tt.com>
Markus Schaber writes:
> 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?
Well, if nonrepeatable or phantom reads would pose a problem because
of those occasional writes, you wouldn't be considering autocommit for
performance reasons either, would you?
regards,
Andreas
--
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: andreas+pg@gate450.dyndns.org, schabi@logix-tt.com
Subject: Re: Read only transactions - Commit or Rollback
In-Reply-To: <87mziwj6na.fsf@gate450.dyndns.org>
* 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