Autocommit off and transaction isolation level - Mailing list pgsql-hackers

From Michael Paesold
Subject Autocommit off and transaction isolation level
Date
Msg-id 007e01c2b25a$9858c370$0a1afea9@beeblebrox
Whole thread Raw
In response to pg_dump.options.diff  ("Serguei Mokhov" <mokhov@cs.concordia.ca>)
Responses Re: Autocommit off and transaction isolation level
List pgsql-hackers
Hi all,

I have come across some weird behavior in postgres concerning autocommit=off
and setting the transaction isolation level. I have no explanation why
things should work as they do, so I consider this a bug, no?

With autocommit=on and normal begin; ... commit; block setting the
transaction isolation level works fine:

billing=# begin;
BEGIN
billing=# set transaction isolation level serializable;
SET
billing=# show transaction isolation level;TRANSACTION ISOLATION LEVEL
-----------------------------SERIALIZABLE
(1 row)

billing=# commit;
COMMIT


Now setting autocommit=off the set transaction isolation level command does
not show any effect:

billing=# set autocommit to off;
SET
billing=# set transaction isolation level serializable;
SET
billing=# select current_date;   date
------------2003-01-02
(1 row)

billing=# show transaction isolation level;TRANSACTION ISOLATION LEVEL
-----------------------------READ COMMITTED    <---- this should be SERIALIZABLE, no??
(1 row)

billing=# commit;
COMMIT

Is it a bug?
Regards,
Michael Paesold



pgsql-hackers by date:

Previous
From: Manfred Koizar
Date:
Subject: Re: pg_dump.options.diff
Next
From: Dan Langille
Date:
Subject: Re: PostgreSQL Password Cracker