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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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.
From | Date | Subject | |
---|---|---|---|
Next Message | Dennis Björklund | 2003-01-02 16:44:56 | Re: PostgreSQL Password Cracker |
Previous Message | Justin Clift | 2003-01-02 14:59:23 | Re: PostgreSQL Password Cracker |
From | Date | Subject | |
---|---|---|---|
Next Message | Patric Bechtel | 2003-01-02 17:34:47 | Fwd: Patch for streaming resultsets |
Previous Message | Tom Lane | 2003-01-02 14:33:20 | Re: Autocommit off and transaction isolation level |