"bad key in cancel request"

From: Neil Conway <neilc(at)samurai(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: "bad key in cancel request"
Date: 2007-11-04 02:35:20
Message-ID: 1194143720.9352.8.camel@goldbach
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I noticed that processCancelRequest() emits a log message at DEBUG2 when
it receives a cancel request with a bad key or for a non-existent PID.
For example,

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?

-Neil

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-11-04 03:06:21 Profiling vs autovacuum (was Re: building 8.3beta2 w/ 'make check' consumes A LOT of disk space)
Previous Message Tom Lane 2007-11-04 01:21:20 Re: should I worry?