From: Adrian Klaver <adrian.klaver@gmail.com>
To: Marcin Krawczyk <jankes.mk@gmail.com>
Cc: pgsql-sql@postgresql.org <pgsql-sql@postgresql.org>
Subject: Re: transaction isolationa level - SERIALIZABLE
Date: Mon, 13 May 2013 07:31:14 -0700
Message-ID: <5190F932.4010909@gmail.com> (raw)
In-Reply-To: <CABnqL315jZq0oJtPCwGwFyqJPh5Y3WGz-0Ld=kNgfAz_sf4-Wg@mail.gmail.com>
References: <CABnqL315jZq0oJtPCwGwFyqJPh5Y3WGz-0Ld=kNgfAz_sf4-Wg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
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
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-sql@postgresql.org
Cc: adrian.klaver@gmail.com, jankes.mk@gmail.com
Subject: Re: transaction isolationa level - SERIALIZABLE
In-Reply-To: <5190F932.4010909@gmail.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