Date: Wed, 03 Dec 2025 15:29:44 +0900 (JST)
Message-Id: <20251203.152944.425772962379417344.ishii@postgresql.org>
To: zam6ak@gmail.com
Cc: pengbo@sraoss.co.jp, pgpool-general@lists.postgresql.org
Subject: Re: "buffer overflow detected" when running SHOW POOL_STATUS
From: Tatsuo Ishii <ishii@postgresql.org>
In-Reply-To: 
 <CAEy4EGXZpB6kx+XQ4SBPJybXKrZ0q5_z4JoSkSjxD9wb6jOJkQ@mail.gmail.com>
References: 
 <CAEy4EGXPw9cU6C6TSCK1FODs0ZK3P3COmsoGU69UFzWeip4b_w@mail.gmail.com>
	<20251202.140205.427777414210613577.ishii@postgresql.org>
	<CAEy4EGXZpB6kx+XQ4SBPJybXKrZ0q5_z4JoSkSjxD9wb6jOJkQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/20251203.152944.425772962379417344.ishii%40postgresql.org>
Precedence: bulk

>> I found a bug with SHOW POOL_STATUS (and pcp_pool_status). The bug
>> broke the data segment used for the conversion from binary form of
>> backend flag (in this case ALWAYS_PRIMARY. Other flag does not raise
>> the issue) to string representation, which caused the buffer overflow
>> issue.
>>
>> Attached is the patch to fix the issue.
> 
> Ishii-san
> 
> Thank you for finding the bug and fixing it...
> 
> I think this bug warrants a new patch release or a rebuild so we can
> use the latest 4.6 in production...
> Is it possible to release a new RPM build 4.6.4-2 or 4.6.5?

According to our package manager (Peng Bo), she is planning to release
updated4.6.4 RPM for Rocky Linux 10 later this month.

Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp