On Thu, Dec 20, 2012 at 4:03 PM, Stephen Touset
wrote:
> I'm having difficulty locating the source of a problem our webapp has been
> running into. Multiple Google searches have failed me, so I'm hoping someone
> here can help troubleshoot.
>
> When some clients (psql, the webapp) connect to our
I'm having difficulty locating the source of a problem our webapp has been
running into. Multiple Google searches have failed me, so I'm hoping someone
here can help troubleshoot.
When some clients (psql, the webapp) connect to our production database, they
become stuck in an aborted transactio
I'm having difficulty locating the source of a problem our webapp has been
running into. Multiple Google searches have failed me, so I'm hoping someone
here can help troubleshoot.
When some clients (psql, the webapp) connect to our production database, they
become stuck in an aborted transactio
On Thu, Dec 20, 2012 at 7:04 PM, Stephen Touset
wrote:
> On Dec 20, 2012, at 3:40 PM, Rob Sargent 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
>AUTOCO
On Dec 20, 2012, at 3:40 PM, Rob Sargent 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 aut
On 12/20/2012 04:33 PM, Stephen Touset wrote:
On Dec 20, 2012, at 3:27 PM, Adrian Klaver wrote:
When on (the default), each SQL command is automatically committed upon
successful completion. To postpone commit in this mode, you must enter a BEGIN
or START TRANSACTION SQL command. When off o
On Dec 20, 2012, at 3:27 PM, Adrian Klaver wrote:
> When on (the default), each SQL command is automatically committed upon
> successful completion. To postpone commit in this mode, you must enter a
> BEGIN or START TRANSACTION SQL command. When off or unset, SQL commands are
> not co
On Dec 20, 2012, at 3:27 PM, Adrian Klaver wrote:
> When on (the default), each SQL command is automatically committed upon
> successful completion. To postpone commit in this mode, you must enter a
> BEGIN or START TRANSACTION SQL command. When off or unset, SQL commands are
> not committed
On 12/20/2012 03:11 PM, Stephen Touset wrote:
I'm having difficulty locating the source of a problem our webapp has
been running into. Multiple Google searches have failed me, so I'm
hoping someone here can help troubleshoot.
I also don't encounter the issue if I connect to the running 9.2
dae
I'm having difficulty locating the source of a problem our webapp has
been running into. Multiple Google searches have failed me, so I'm
hoping someone here can help troubleshoot.
When some clients (psql, the webapp) connect to our production
database, they become stuck in an aborted transaction a
10 matches
Mail list logo
