| From: | zam bak <zam6ak(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgpool-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: "buffer overflow detected" when running SHOW POOL_STATUS |
| Date: | 2025-12-02 17:31:46 |
| Message-ID: | CAEy4EGXZpB6kx+XQ4SBPJybXKrZ0q5_z4JoSkSjxD9wb6jOJkQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgpool-general |
On Tue, Dec 2, 2025 at 12:02 AM Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>
> >> 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.
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?
Regards
Z....
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS K.K.
> English: http://www.sraoss.co.jp/index_en/
> Japanese:http://www.sraoss.co.jp
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2025-12-03 06:29:44 | Re: "buffer overflow detected" when running SHOW POOL_STATUS |
| Previous Message | Tatsuo Ishii | 2025-12-02 05:02:05 | Re: "buffer overflow detected" when running SHOW POOL_STATUS |