Skip site navigation (1) Skip section navigation (2)

Re: Read only transactions - Commit or Rollback

From: Markus Schaber <schabi(at)logix-tt(dot)com>
To: PostgreSQL Performance List <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Read only transactions - Commit or Rollback
Date: 2005-12-20 12:31:53
Message-ID: 43A7F9B9.3010906@logix-tt.com (view raw or flat)
Thread:
Lists: pgsql-performance
Hello, Andreas,

Andreas Seltenreich wrote:


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

Yes, the question is purely performance-wise. We don't care about any
read/write conflicts in this special case.

Some time ago, I had some tests with large bulk insertions, and it
turned out that SERIALIZABLE seemed to be 30% faster, which surprised us.

That's why I ask this questions, and mainly because we currently cannot
perform a large bunch of benchmarking.

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

In response to

Responses

pgsql-performance by date

Next:From: Nicolas BarbierDate: 2005-12-20 13:06:15
Subject: Re: Read only transactions - Commit or Rollback
Previous:From: Andreas SeltenreichDate: 2005-12-20 12:27:05
Subject: Re: Read only transactions - Commit or Rollback

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group