From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | 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 16:33:01 |
Message-ID: | CAKFQuwbTV2EimKMm5uRpu0GUx5CQKwp1YKAiXB2Adt3X1TEnGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Jan 1, 2016 at 9:19 AM, Guillaume Lelarge <guillaume(at)lelarge(dot)info>
wrote:
> Hi,
>
> 2016-01-01 16:10 GMT+01:00 <floriparob(at)gmail(dot)com>:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 13841
>> Logged by: ROBERT
>> Email address: floriparob(at)gmail(dot)com
>> PostgreSQL version: 9.5rc1
>> Operating system: Debian stretch/sid
>> Description:
>>
>>>
>>>
>> timemanager=> set autocommit off;
>>
>>
> Thought that I'd made a typo but entered as per doco.
>>
>>
> There's no autocommit GUC. You probably want to use the AUTOCOMMIT
> internal variable of psql. In which case, you should do :
>
> \set AUTOCOMMIT off
>
> Definitely not a bug
>
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. But indeed the behavior is client-side only and so it
makes no sense to try and control it via SQL - which is what the command
"SET" is from.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-01-01 17:04:33 | Re: BUG #13841: Unable to set autocommit in psql |
Previous Message | Guillaume Lelarge | 2016-01-01 16:19:18 | Re: BUG #13841: Unable to set autocommit in psql |