| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "PostgreSQL-documentation" <pgsql-docs(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] statement_timeout logging |
| Date: | 2005-09-17 07:02:23 |
| Message-ID: | KGEFLMPJFBNNLNOOOPLGKEFICJAA.simon@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
>Alvaro Herrera
> On Fri, Sep 16, 2005 at 03:41:11PM -0400, Bruce Momjian 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?
Yes, my patch. :-)
The message is generated following receipt of a SIGINT which is sent by
kill() after the statement_timeout.
My patch was able to generate a different message by logging just before
the kill() is called. (Obviously, there isn't much "after" in this
circumstance).
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-09-18 23:34:32 | Docs on CE? |
| Previous Message | Bruce Momjian | 2005-09-17 04:31:16 | Re: [HACKERS] statement_timeout logging |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2005-09-17 12:47:00 | Re: Beta2 Wrap Up ... |
| Previous Message | Simon Riggs | 2005-09-17 06:58:07 | Re: statement_timeout logging |