| From: | Stephen Touset <stephen(dot)touset(at)onelogin(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Implicit transaction not rolling back after error |
| Date: | 2012-12-21 02:04:38 |
| Message-ID: | 3DF6FE9B-425F-4B6A-8D3E-F46FA455C06F@onelogin.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Dec 20, 2012, at 3:40 PM, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
> On 12/20/2012 04:33 PM, Stephen Touset wrote:
>
>> So yes, AUTOCOMMIT is definitely on.
>
> What does \set show when entered from the psql command line?
test=> \set
AUTOCOMMIT = 'OFF'
*facepalm*.
Turns out someone put a .psqlrc with autocommit off in /etc/skel when the box was originally set up as a replacement for our previous app server. Account users were created afterwards, and the change propagated to our application account as well as all of our individual accounts.
Why, though, would `SHOW AUTOCOMMIT` lie? And `SET AUTOCOMMIT TO off` says that capability is disabled. So how does the config file manage to do it?
Thanks for the insight!
--
Stephen Touset
Senior Software Engineer
stephen(dot)touset(at)onelogin(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2012-12-21 02:22:21 | Re: Implicit transaction not rolling back after error |
| Previous Message | David Johnston | 2012-12-21 01:48:51 | Re: Using POSIX Regular Expressions on xml type fields gives inconsistent results |