| From: | Yishai Tamir <yishaitamir(at)live(dot)com> |
|---|---|
| To: | "pgpool-hackers(at)lists(dot)postgresql(dot)org" <pgpool-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | [PATCH] Downgrade elog(LOG) to elog(DEBUG1) for pi->node_ids in get_pools() |
| Date: | 2026-03-04 18:39:27 |
| Message-ID: | SV0P279MB0514A33CA35ECDDA515E7F82C37CA@SV0P279MB0514.NORP279.PROD.OUTLOOK.COM |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgpool-hackers |
Hi,
The attached patch downgrades an elog(LOG) to elog(DEBUG1) in get_pools()
(src/utils/pool_process_reporting.c).
The elog statement was added in commit 706ca859c as part of the
pgpool_adm_pcp_proc_info feature. It prints pi->node_ids bitmap values
at LOG level for every connection on every backend whenever pool status
is queried.
In containerized deployments where a metrics exporter (pgpool2_exporter)
continuously polls "show pool_pools", this produces thousands of log
lines per minute. We confirmed the fix eliminates the spam on our
staging cluster under real production-like traffic.
Since the message is purely diagnostic, DEBUG1 is the appropriate level.
GitHub issue: https://github.com/pgpool/pgpool2/issues/153
Regards,
Yishai Tamir
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Downgrade-elog-LOG-to-elog-DEBUG1-for-pi-node_ids-in.patch | application/octet-stream | 1.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2026-03-05 04:16:02 | Re: [PATCH] Downgrade elog(LOG) to elog(DEBUG1) for pi->node_ids in get_pools() |
| Previous Message | Tatsuo Ishii | 2026-03-02 01:00:28 | Close listening socokets before forking |