Re: "bad key in cancel request"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "bad key in cancel request"
Date: 2007-11-04 16:06:02
Message-ID: 14028.1194192362@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Neil Conway <neilc(at)samurai(dot)com> writes:
> ereport(DEBUG2,
> (errmsg_internal("bad key in cancel request for process %d",
> backendPID)));

> I think this ought to be logged at a higher level than DEBUG2: for one
> thing, it is a potential security issue the DBA might want to be aware
> of. It could also indicate a misconfigured or buggy client application.
> Therefore, I think we should raise the level to WARNING, or perhaps
> NOTICE. Any objections?

No, if it's intended for the log it should be LOG. Your other proposals
are actually *less* likely to get to where the DBA could see them.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message ohp 2007-11-04 16:26:02 Re: should I worry?
Previous Message Bruce Momjian 2007-11-04 15:43:32 Re: Segmentation fault using digest from pg_crypto