Statement timeout logging - Mailing list pgsql-hackers

From Thom Brown
Subject Statement timeout logging
Date
Msg-id CAA-aLv7gt0HbzVnspWv6wqBD2Bz0YT02JdA3t+53ZxoUvKxdTw@mail.gmail.com
Whole thread Raw
Responses Re: Statement timeout logging  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
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?

--
Thom



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Hard limit on WAL space used (because PANIC sucks)
Next
From: Gurjeet Singh
Date:
Subject: Re: Processing long AND/OR lists