| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Michael Paesold" <mpaesold(at)gmx(dot)at> |
| Cc: | "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Autocommit off and transaction isolation level |
| Date: | 2003-01-02 14:33:20 |
| Message-ID: | 19946.1041518000@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2003-01-02 14:59:23 | Re: PostgreSQL Password Cracker |
| Previous Message | Tom Lane | 2003-01-02 14:29:39 | Re: pg_dump.options.diff |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-01-02 15:39:02 | Re: Autocommit off and transaction isolation level |
| Previous Message | Tom Lane | 2003-01-02 14:29:39 | Re: pg_dump.options.diff |