Re: "stuck spinlock"

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Christophe Pettus <xof(at)thebuild(dot)com>
Cc: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "stuck spinlock"
Date: 2013-12-13 03:40:46
Message-ID: CAM3SWZQq0EC49BNPNSaqNmd_01W4aZz5s1BmJcZKCgM8p972JQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 12, 2013 at 7:35 PM, Christophe Pettus <xof(at)thebuild(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2013-12-13 03:48:03 Re: [PATCH] configure: allow adding a custom string to PG_VERSION
Previous Message Christophe Pettus 2013-12-13 03:35:36 Re: "stuck spinlock"