Re: [HACKERS] statement_timeout logging

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] statement_timeout logging
Date: 2005-09-16 19:41:11
Message-ID: 200509161941.j8GJfB122512@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

pgman wrote:
> Simon Riggs wrote:
> > Currently, when we set a statement_timeout and a query runs over that
> > time there is no log message to say that the statement has timed out. We
> > do get a message which says
> > ERROR: canceling query due to user request
> > and so in the server log it is impossible to tell the difference between
> > a query that has been cancelled deliberately by the user and a query
> > whose time(out) has come.
>
> I have updated the message to:
>
> errmsg("canceling query due to user request or statement timeout")));

Oops. Did we freeze the message strings already for this release?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2005-09-16 19:52:37 Re: [PATCHES] Caveat for Domains
Previous Message Tom Lane 2005-09-12 19:31:04 Re: Multicolumn index doc out of date?

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonah H. Harris 2005-09-16 20:41:39 Re: Why does VACUUM FULL bother locking pages?
Previous Message Stephen Frost 2005-09-16 19:36:29 Re: Spinlocks, yet again: analysis and proposed patches