Re: [HACKERS] statement_timeout logging

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] statement_timeout logging
Date: 2005-09-16 20:54:55
Message-ID: 20050916205455.GA9069@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On Fri, Sep 16, 2005 at 03:41:11PM -0400, Bruce Momjian wrote:
> pgman wrote:

> > 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?

Not yet.

I'm not sure I agree with the wording though -- is there no way to tell
the difference?

--
Alvaro Herrera -- Valdivia, Chile Architect, www.EnterpriseDB.com
"No single strategy is always right (Unless the boss says so)"
(Larry Wall)

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2005-09-17 04:31:16 Re: [HACKERS] statement_timeout logging
Previous Message Bruce Momjian 2005-09-16 19:52:37 Re: [PATCHES] Caveat for Domains

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2005-09-16 21:07:34 Re: Why does VACUUM FULL bother locking pages?
Previous Message Jonah H. Harris 2005-09-16 20:41:39 Re: Why does VACUUM FULL bother locking pages?