[pgpool-hackers: 4350] Downgrading some normal ERROR messages

[Bo Peng]

I created a patch to downgrade the following ERROR messages:

(1) ERROR:unable to flush data to frontend

(2) ERROR:  unable to read data from frontend
    DETAIL:  EOF encountered with frontend

(3) ERROR:  unable to read data
    DETAIL:  child connection forced to terminate due to client_idle_limit:30 is reached


(1) and (2)
These messages are cuased when the client did not send a terminate message
before disconnecting to pgpool.
For example, when the client process was forcefully terminated, the error occurs.
Although they are harmless, it can sometimes confuse users.

(3) 
If we set "client_idle_limit" to a non-zero value, the connection
will be disconnected if it remains idle since the last query.

The disconnection is caused by Pgpool-II settings,
but Pgpool-II handles the log message as an "ERROR".


Because the ERROR messages above are normal messages,
I would suggest downgrading them:

(1) and (2) -> DEBUG
(3)         -> LOG


Patch is attached.
Any comments?

-- 
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS LLC
TEL: 03-5979-2701 FAX: 03-5979-2702
URL: https://www.sraoss.co.jp/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: downgrade_error_messages_v1.patch
Type: application/octet-stream
Size: 8083 bytes
Desc: not available
URL: <http://www.pgpool.net/pipermail/pgpool-hackers/attachments/20230616/933db426/attachment.obj>