pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedtransaction isolationa level - SERIALIZABLE
3+ messages / 2 participants
[nested] [flat]
* transaction isolationa level - SERIALIZABLE
@ 2013-05-13 09:22 Marcin Krawczyk <jankes.mk@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Marcin Krawczyk @ 2013-05-13 09:22 UTC (permalink / raw)
To: pgsql-sql
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)
regards
mk
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: transaction isolationa level - SERIALIZABLE
@ 2013-05-13 14:31 Adrian Klaver <adrian.klaver@gmail.com>
parent: Marcin Krawczyk <jankes.mk@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Adrian Klaver @ 2013-05-13 14:31 UTC (permalink / raw)
To: Marcin Krawczyk <jankes.mk@gmail.com>; +Cc: pgsql-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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: transaction isolationa level - SERIALIZABLE
@ 2013-05-13 22:25 Marcin Krawczyk <jankes.mk@gmail.com>
parent: Adrian Klaver <adrian.klaver@gmail.com>
0 siblings, 0 replies; 3+ messages in thread
From: Marcin Krawczyk @ 2013-05-13 22:25 UTC (permalink / raw)
To: Adrian Klaver <adrian.klaver@gmail.com>; +Cc: pgsql-sql
That's what I thought. Thank you.
regards
mk
2013/5/13 Adrian Klaver <adrian.klaver@gmail.com>
> 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<http://www.postgresql.org/...;
>
> "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
>
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2013-05-13 22:25 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-05-13 09:22 transaction isolationa level - SERIALIZABLE Marcin Krawczyk <jankes.mk@gmail.com>
2013-05-13 14:31 ` Adrian Klaver <adrian.klaver@gmail.com>
2013-05-13 22:25 ` Marcin Krawczyk <jankes.mk@gmail.com>
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