回复: Fix potential overflow risks from wcscpy and sprintf - Mailing list pgsql-hackers

From Yan Haibo
Subject 回复: Fix potential overflow risks from wcscpy and sprintf
Date
Msg-id CH3PR08MB86106155FA780BFAFE3433A0FA70A@CH3PR08MB8610.namprd08.prod.outlook.com
Whole thread Raw
In response to Re: Fix potential overflow risks from wcscpy and sprintf  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: 回复: Fix potential overflow risks from wcscpy and sprintf
List pgsql-hackers
Thank you. Peter. It seems the patch may have been lost during our earlier communication, so I’ve reattached it here.
I hope it comes through correctly this time.
Best regards,
Haibo



发件人: Peter Eisentraut <peter@eisentraut.org>
发送时间: 2025年6月11日 00:43
收件人: Yan Haibo <haibo.yan@hotmail.com>; pgsql-hackers@lists.postgresql.org <pgsql-hackers@lists.postgresql.org>
主题: Re: Fix potential overflow risks from wcscpy and sprintf
 
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.

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Per-role disabling of LEAKPROOF requirements for row-level security?
Next
From: Yan Haibo
Date:
Subject: 回复: Fix potential overflow risks from wcscpy and sprintf