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

Re: Autocommit off and transaction isolation level

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paesold <mpaesold(at)gmx(dot)at>,PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Autocommit off and transaction isolation level
Date: 2003-01-02 15:39:02
Message-ID: 20030102073752.U90763-100000@megazone23.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Thu, 2 Jan 2003, Tom Lane wrote:

> "Michael Paesold" <mpaesold(at)gmx(dot)at> writes:
> > 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
>
> SET does not start a transaction block, so this will not work.  You must
> use an explicit BEGIN before setting TRANSACTION ISOLATION LEVEL.
>
> You might instead set default_transaction_isolation to get the behavior
> I think you are looking for.

The overall behavior appears to be against spec, but I figure this was
discussed at the time the set transation was added.



In response to

pgsql-hackers by date

Next:From: Dennis BjörklundDate: 2003-01-02 16:44:56
Subject: Re: PostgreSQL Password Cracker
Previous:From: Justin CliftDate: 2003-01-02 14:59:23
Subject: Re: PostgreSQL Password Cracker

pgsql-patches by date

Next:From: Patric BechtelDate: 2003-01-02 17:34:47
Subject: Fwd: Patch for streaming resultsets
Previous:From: Tom LaneDate: 2003-01-02 14:33:20
Subject: Re: Autocommit off and transaction isolation level

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