From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200509161941.j8GJfB122512@candle.pha.pa.us>
Subject: Re: [HACKERS] statement_timeout logging
In-Reply-To: 
To: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Date: Fri, 16 Sep 2005 15:41:11 -0400 (EDT)
Cc: Simon Riggs <simon@2ndquadrant.com>, pgsql-hackers@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

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@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073