[pgpool-general: 6622] Re: Fwd: A lot of "checking zapping sent message" in log

Bo Peng pengbo at sraoss.co.jp
Tue Jul 2 10:00:07 JST 2019


Hello,

On Fri, 28 Jun 2019 09:44:56 +0300
Vitaly Voronov <wizard1024 at gmail.com> wrote:

> Hi, all.
> 
> We uses PostgreSQL JDBC Driver 42.2.6 via pgpool-II version 4.0.5
> (torokiboshi) on CentOS 7 (from pgpool repo -
> pgpool-II-pg11.4.0.5-1pgdg.rhel7) for connecting to PostgreSQL 11 (from
> postgresql.org repo - postgresql11-server.x86_64.11.3-1PGDG.rhel7).
> 
> We see a lot of messages in log file:
> Jun 28 15:31:07 app1 pgpool[12527]: 2019-06-28 15:31:07: pid 15087: LOG:
>  checking zapping sent message: 0x1ef8958 query_context: 0x1efc598
> Jun 28 15:31:07 app1 pgpool[12527]: 2019-06-28 15:31:07: pid 15087: LOG:
>  checking zapping sent message: 0x1ef8960 query_context: 0x1efe0a8
> Jun 28 15:31:07 app1 pgpool[12527]: 2019-06-28 15:31:07: pid 15087: LOG:
>  checking zapping sent message: 0x1ef8968 query_context: 0x1efb588
> Jun 28 15:31:07 app1 pgpool[12527]: 2019-06-28 15:31:07: pid 15087: LOG:
>  checking zapping sent message: 0x1ef8970 query_context: 0x1efb588
> Jun 28 15:31:15 app1 pgpool[12527]: 2019-06-28 15:31:15: pid 14888: LOG:
>  checking zapping sent message: 0x1ef8958 query_context: 0x1efb588
> Jun 28 15:31:15 app1 pgpool[12527]: 2019-06-28 15:31:15: pid 14888: LOG:
>  checking zapping sent message: 0x1ef8960 query_context: 0x1efad78
> Jun 28 15:31:15 app1 pgpool[12527]: 2019-06-28 15:31:15: pid 14888: LOG:
>  checking zapping sent message: 0x1ef8968 query_context: 0x1eff668
> Jun 28 15:31:15 app1 pgpool[12527]: 2019-06-28 15:31:15: pid 14888: LOG:
>  checking zapping sent message: 0x1ef8970 query_context: 0x1eff668
> Jun 28 15:31:28 app1 pgpool[12527]: 2019-06-28 15:31:28: pid 15090: LOG:
>  checking zapping sent message: 0x1ef8958 query_context: 0x1efd898
> Jun 28 15:31:28 app1 pgpool[12527]: 2019-06-28 15:31:28: pid 15090: LOG:
>  checking zapping sent message: 0x1ef8960 query_context: 0x1efd898
> 
> I've enabled all logging on pgpool, but we couldn't find any dependency
> between executed query and messages in logs.
> 
> Can you explain situation, which can cause such messages?

"checking zapping sent message" is a normal message.

When Pgpool-II receive CommandComplete message from backend,
the query which is not referenced by others and is unnamed statement/portal,
will be removed from query context.

Because it is a normal message, we downgraded it from "LOG" to "DEBUG5".
https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=d86c71d163c7f495e08db9055fa6bdd39e57a1ac
 
> With best regard, Vitaly.


-- 
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan



More information about the pgpool-general mailing list