Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from
	<pgsql-sql-owner+M37284=pgsql+2Dsql=arkaria.postgresql.org@postgresql.org>)
	id 1Ubtmg-00057L-LR
	for pgsql-sql@arkaria.postgresql.org; Mon, 13 May 2013 14:31:26 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.72) (envelope-from
	<pgsql-sql-owner+M37284=pgsql+2Dsql=arkaria.postgresql.org@postgresql.org>)
	id 1Ubtmg-0001wc-0x
	for pgsql-sql@arkaria.postgresql.org; Mon, 13 May 2013 14:31:26 +0000
Received: from makus.postgresql.org ([2001:4800:7903:4::125])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <adrian.klaver@gmail.com>) id 1Ubtme-0001vw-SI
	for pgsql-sql@postgresql.org; Mon, 13 May 2013 14:31:25 +0000
Received: from mail-pd0-f171.google.com ([209.85.192.171])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <adrian.klaver@gmail.com>) id 1UbtmY-0000SQ-Nz
	for pgsql-sql@postgresql.org; Mon, 13 May 2013 14:31:24 +0000
Received: by mail-pd0-f171.google.com with SMTP id r11so4483639pdi.30
	for <pgsql-sql@postgresql.org>; Mon, 13 May 2013 07:31:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=x-received:message-id:date:from:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=swz6YPLFOBVQoLf/EDVlE3Y3XOMy/94kIuy1r/0GkCQ=;
	b=EV+/tdoR1RfePhIQvYJKzgq25YV6LRmxdzbs9m644JydMdKNcspQY3EQdDfzy8n1IK
	gWZVDlkrSMuRQ2kkDjeu620Pz7PcncwC3OpcTE75KU0jj2fjzux9fxRFdKslvoQsnNtN
	w9HAY4DL5qOYsZa5v0Ylur8othhNXynhak6uPwZZ1BkbVDk61XXI0oUu5WSVgRTR3bSI
	x/TlmX6jkIqfqqaqtuig1huwebkp+y5QmnjMM5xvD7zLhJdDDMDuD6r8U0wx0T08bre1
	qfngL8qq5rv5ZQm/tm+5CjiiIlAUlTeZSXQt5bS3iF6OX6Fdkisicytd/JzzSQbFGcNz
	xsrQ==
X-Received: by 10.68.191.167 with SMTP id gz7mr30183584pbc.16.1368455478167;
	Mon, 13 May 2013 07:31:18 -0700 (PDT)
Received: from [192.168.1.2] (174-21-199-249.tukw.qwest.net. [174.21.199.249])
	by mx.google.com with ESMTPSA id
	wt5sm14257794pbc.38.2013.05.13.07.31.15 for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 13 May 2013 07:31:16 -0700 (PDT)
Message-ID: <5190F932.4010909@gmail.com>
Date: Mon, 13 May 2013 07:31:14 -0700
From: Adrian Klaver <adrian.klaver@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
	rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Marcin Krawczyk <jankes.mk@gmail.com>
CC: "pgsql-sql@postgresql.org" <pgsql-sql@postgresql.org>
Subject: Re: transaction isolationa level - SERIALIZABLE
References: 
 <CABnqL315jZq0oJtPCwGwFyqJPh5Y3WGz-0Ld=kNgfAz_sf4-Wg@mail.gmail.com>
In-Reply-To: 
 <CABnqL315jZq0oJtPCwGwFyqJPh5Y3WGz-0Ld=kNgfAz_sf4-Wg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -0.1 (/)
List-Archive: <http://archives.postgresql.org/pgsql-sql>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-sql.postgresql.org>
List-Owner: <mailto:pgsql-sql-owner@postgresql.org>
List-Post: <mailto:pgsql-sql@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-sql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
X-Mailing-List: pgsql-sql
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

On 05/13/2013 02:22 AM, Marcin Krawczyk wrote:
> Hi list,
>
> I have some problems with SERIALIZABLE isolation level, namely my users
> are plagued with concurrency errors. As of postgres 9.1 (which I'm
> running) there has been a change to SERIALIZABLE logic, unfortunately my
> application has not been updated to work with the new logic. I don't
> have an access to it's code and the only thing I can do is to report the
> issue to the authors. But before I do it, since I don't actually
> need SERIALIZABLE for my use, is it possible to have transactions always
> run in default READ COMMITTED mode, regardless of application level SET
> SESSION CHARACTERISTICS AS TRANSACTION command ... ? (like e.g in
> postgres 8.1 where SERIALIZABLE = READ COMMITED)

I don't think so:

http://www.postgresql.org/docs/9.1/interactive/config-setting.html

"Furthermore, it is possible to assign a set of parameter settings to a 
user or a database. Whenever a session is started, the default settings 
for the user and database involved are loaded. The commands ALTER ROLE 
and ALTER DATABASE, respectively, are used to configure these settings. 
Per-database settings override anything received from the postgres 
command-line or the configuration file, and in turn are overridden by 
per-user settings; both are overridden by per-session settings.

>
>
> regards
> mk


-- 
Adrian Klaver
adrian.klaver@gmail.com


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql