[pgpool-committers: 9618] pgpool: Downgrading some normal ERROR messages to DEBUG messages.

Bo Peng pengbo at sraoss.co.jp
Thu Nov 9 21:59:41 JST 2023

Downgrading some normal ERROR messages to DEBUG messages.

The following ERROR messages are downgraded to DEBUG 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.

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 decide to downgrade them.

Discussion: https://www.pgpool.net/pipermail/pgpool-hackers/2023-June/004351.html



Modified Files
src/include/utils/elog.h          |  6 ++++--
src/include/utils/fe_ports.h      |  6 ++++--
src/protocol/pool_process_query.c | 14 +++++++-------
src/tools/fe_port.c               |  2 ++
src/utils/error/elog.c            | 21 ++++++++++++++++++---
src/utils/pool_stream.c           |  6 +++---
6 files changed, 38 insertions(+), 17 deletions(-)

More information about the pgpool-committers mailing list