Re: BUG #13841: Unable to set autocommit in psql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Guillaume Lelarge <guillaume(at)lelarge(dot)info>, rob stone <floriparob(at)gmail(dot)com>, PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13841: Unable to set autocommit in psql
Date: 2016-01-01 17:04:33
Message-ID: 10012.1451667873@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>> 2016-01-01 16:10 GMT+01:00 <floriparob(at)gmail(dot)com>:
>>> Thought that I'd made a typo but entered as per doco.

> Though when referencing the documentation in a report like this it is
> generally helpful to provide a link to said documentation so it at least
> can be checked.

Indeed. "set autocommit to off" hasn't been supported since PG 7.3, more
than ten years ago. So if there's still some documentation somewhere
recommending that, we really need to find and fix it.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-01-01 20:30:35 Re: BUG #13840: pg_dump generates unloadable SQL when third party string type index option is used
Previous Message David G. Johnston 2016-01-01 16:33:01 Re: BUG #13841: Unable to set autocommit in psql