Re: "stuck spinlock" - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: "stuck spinlock"
Date
Msg-id CAM3SWZQq0EC49BNPNSaqNmd_01W4aZz5s1BmJcZKCgM8p972JQ@mail.gmail.com
Whole thread Raw
In response to Re: "stuck spinlock"  (Christophe Pettus <xof@thebuild.com>)
Responses Re: "stuck spinlock"
List pgsql-hackers
On Thu, Dec 12, 2013 at 7:35 PM, Christophe Pettus <xof@thebuild.com> wrote:
> There are a *lot* of "canceling statement due to statement timeout" messages, which is interesting, because:
>
> postgres=# show statement_timeout;
>  statement_timeout
> -------------------
>  0
> (1 row)

Couldn't that just be the app setting it locally? In fact, isn't that
the recommended usage?


-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: "stuck spinlock"
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] configure: allow adding a custom string to PG_VERSION