[pgpool-hackers: 4178] Re: [pgpool-committers: 8688] pgpool: Enable debug1 while executing 074.bug700_memqcache_segfault.

[Tatsuo Ishii]

we see 074.bug700_memqcache_segfault timeout error again. This time it
seems CloseComplete message was sent from backend but Ready for Query
message is not.  To persuit the cause of the timeout, I enabled the
debug log again.

Best reagards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

From: Tatsuo Ishii <ishii at sraoss.co.jp>
Subject: [pgpool-committers: 8688] pgpool: Enable debug1 while executing 074.bug700_memqcache_segfault.
Date: Fri, 17 Jun 2022 07:38:58 +0000
Message-ID: <E1o26ZG-0001FP-TX at gothos.postgresql.org>

> Enable debug1 while executing 074.bug700_memqcache_segfault.
> 
> This is necessary to pursuit occasional timeout in the test.  Also add
> debug logging to pool_push_pending_data() for the same purpose.
> ereport for debugging to
> 
> Branch
> ------
> master
> 
> Details
> -------
> https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=582e1beee52fb0bfd63090e3d8686f23194f5c8b
> 
> Modified Files
> --------------
> src/protocol/pool_process_query.c                               | 3 +++
> src/test/regression/tests/074.bug700_memqcache_segfault/test.sh | 1 +
> 2 files changed, 4 insertions(+)
>