public inbox for [email protected]  
help / color / mirror / Atom feed
From: JOSE MARIA Marin <[email protected]>
To: [email protected]
Subject: Bug report: Hardcoded debug logs "pi->node_ids" in pcp_child (v4.7.0)
Date: Mon, 6 Apr 2026 13:14:36 +0200
Message-ID: <CAA2mqj9mhQJTH3xvvt3jq99Y1HCKVF66v3Hj5+Zx1Lup33kapA@mail.gmail.com> (raw)

*Description:* After upgrading to PgPool-II 4.7.0, the logs are being
flooded with internal debug messages every time pcp_proc_info is executed.

*Log Example:* pcp_child pid XXXX: LOG: pi->node_ids[0]:1
pi->node_ids[1]:0. Repeats tens of times.
...
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:1
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:1
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
2026-04-06 11:11:03.367: psql pid 188: LOG:  pi->node_ids[0]:3
pi->node_ids[1]:0
...

*Steps to reproduce:*

   1.

   Run PgPool-II 4.7.0.
   2.

   Execute pcp_proc_info.
   3.

   Check the main PgPool log.

*Current behavior:* Even with log_min_messages = warning and log_pcp_messages
= off, these messages persist. It seems like a hardcoded pool_log or fprintf
in the source code of the PCP child handler.

*Expected behavior:* Internal structure debugging like pi->node_ids should
only appear when debug_level is high or during development builds.

*Environment:*

   -

   PgPool-II version: 4.7.0
   -

   OS: Ubuntu (Docker)


reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Bug report: Hardcoded debug logs "pi->node_ids" in pcp_child (v4.7.0)
  In-Reply-To: <CAA2mqj9mhQJTH3xvvt3jq99Y1HCKVF66v3Hj5+Zx1Lup33kapA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox