Re: Statement timeout logging - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Statement timeout logging
Date
Msg-id CAFj8pRA4Q2EtN-TPJAD6ZSsU+nNm009-QuTBwCx2WzwahVQ+9w@mail.gmail.com
Whole thread Raw
In response to Statement timeout logging  (Thom Brown <thom@linux.com>)
Responses Re: Statement timeout logging  (Thom Brown <thom@linux.com>)
List pgsql-hackers
2013/6/6 Thom Brown <thom@linux.com>:
> Hi,
>
> When a statement is cancelled due to it running for long enough for
> statement_timeout to take effect, it logs a message:
>
> ERROR:  canceling statement due to statement timeout
>
> However, it doesn't log what the timeout was at the time of the
> cancellation.  This may be set in postgresql.conf, the database, or on
> the role, but unless log_line_prefix is set to show the database name
> and the user name, there's no reliable way of finding out what context
> the configuration applied from.  Setting log_duration won't help
> either because that only logs the duration of completed queries.
>
> Should we output the statement_timeout value when a query is cancelled?

+1

we use same feature in GoodData. Our long queries are cancelled by
users and we should to known how much a users would to wait.

Regards

Pavel

>
> --
> Thom
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: RFC: ExecNodeExtender
Next
From: Robert Haas
Date:
Subject: Re: MVCC catalog access