0000806: lots of logs pool_pending_message_set_flush_request with level LOG

ID	Project	Category	View Status	Date Submitted	Last Update

0000806	Pgpool-II	General	public	2023-06-29 00:53	2023-08-17 11:18

Reporter	Cactusbone	Assigned To	t-ishii
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	open
Product Version	4.4.3
Target Version	4.4.4	Fixed in Version	4.4.4

Summary	0000806: lots of logs pool_pending_message_set_flush_request with level LOG
Description	Those logs looks like debug logs, however with level LOG, which is after WARNING and ERROR ``` pid 183: LOG: pool_pending_message_set_flush_request: msg: Parse pid 183: LOG: pool_pending_message_set_flush_request: msg: Bind pid 183: LOG: pool_pending_message_set_flush_request: msg: Describe pid 183: LOG: pool_pending_message_set_flush_request: msg: Execute ``` It's possible to disable them using log_min_messages=FATAL (or PANIC), however this seems a bit extreme... > Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, INFO, NOTICE, WARNING, ERROR, LOG, FATAL, and PANIC. I think INFO or DEBUG1 would be better suited. code at src/context/pool_session_context.c#L1728 It seems to have been added "recently" by commit f9521fe49131a0bd7c7d63d6c050c2edfca5155c
Tags	No tags attached.

Date Modified	Username	Field	Change
2023-06-29 00:53	Cactusbone	New Issue
2023-06-29 08:58	t-ishii	Assigned To	=> t-ishii
2023-06-29 08:58	t-ishii	Status	new => assigned
2023-06-29 09:29	t-ishii	Note Added: 0004413
2023-08-17 11:18	administrator	Status	assigned => closed
2023-08-17 11:18	administrator	Fixed in Version	=> 4.4.4
2023-08-17 11:18	administrator	Target Version	=> 4.4.4

t-ishii 2023-06-29 09:29 developer ~0004413	Thank you for pointing it out. Yes, you are absolutely right. Those lines are for debugging and should have been downgraded to DEBUG*. I think DEBUG5 is suitable. Will fix.