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

• Re: Autocommit off and transaction isolation level at 2003-01-02 14:33:20 from Tom Lane

pgsql-hackers by date

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

pgsql-patches by date

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