Re: Fix potential overflow risks from wcscpy and sprintf

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Yan Haibo <haibo(dot)yan(at)hotmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix potential overflow risks from wcscpy and sprintf
Date: 2025-06-11 07:43:59
Message-ID: a822a446-10d6-4305-bae3-0c3100d8cc0c@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06.06.25 22:50, Yan Haibo wrote:
> This change stems from a recent static code analysis, which identified a
> minor potential overflow issue. I would appreciate it if someone could
> review the fix at their convenience.

Please provide more detail in each case what the issue is and how you
are proposing to fix it.

Note that PostgreSQL code is regularly run through various static
analysis tools, so if the issue were super-obvious, it would probably
have been noticed by now.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-06-11 07:58:00 Re: Replace some %llu remnants in the tree
Previous Message jian he 2025-06-11 07:28:36 Re: Add SPLIT PARTITION/MERGE PARTITIONS commands