Fix potential overflow risks from wcscpy and sprintf

From: Yan Haibo <haibo(dot)yan(at)hotmail(dot)com>
To: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Fix potential overflow risks from wcscpy and sprintf
Date: 2025-06-06 20:50:06
Message-ID: CH3PR08MB8610864A5B8E6B1AAB7374FBFA6EA@CH3PR08MB8610.namprd08.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
Thank you for your time and support.
Best regards,
Haibo

Attachment Content-Type Size
0001-Mitigate-potential-overflow-risks-from-wcscpy-and-sp.patch application/octet-stream 2.9 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2025-06-06 21:13:23 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Previous Message Nico Williams 2025-06-06 20:18:50 Re: Unnecessary connection overhead due copy-on-write (mainly openssl)