| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | zam6ak(at)gmail(dot)com |
| Cc: | pgpool-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: "buffer overflow detected" when running SHOW POOL_STATUS |
| Date: | 2025-12-02 05:02:05 |
| Message-ID: | 20251202.140205.427777414210613577.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgpool-general |
>> Unfortunately, I was not able to reproduce the issue on my Ubuntu 24
>> and Rocky Linux 10.1 box (pgpool is compiled from source code).
>> So there are some questions:
>>
>> - Is the issue occurred even when you execute other pgpool command?
>> (for example "show pool_processes")
>
> No. Only getting this issue when running SHOW POOL_STATUS
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.
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| Attachment | Content-Type | Size |
|---|---|---|
| fix_backend_flag.patch | text/x-patch | 816 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | zam bak | 2025-12-02 17:31:46 | Re: "buffer overflow detected" when running SHOW POOL_STATUS |
| Previous Message | zam bak | 2025-12-01 14:42:40 | Re: "buffer overflow detected" when running SHOW POOL_STATUS |