Re: Post-release followup: pg_add_size_overflow()
Jacob Champion <jacob.champion@enterprisedb.com>
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: Chao Li <li.evan.chao@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-11-19T17:45:46Z
Lists: pgsql-hackers
On Tue, Nov 18, 2025 at 5:17 PM Chao Li <li.evan.chao@gmail.com> wrote: > I just reviewed the patch. Overall looks solid to me. Thanks for the review! > Putting “…” inside a function body looks quite uncommon. I searched over the source tree and couldn't find other occurrence. As the comment has explained why omitting pg_neg_size_overflow, maybe just remove the entry #if 0 block, or just leave an empty function body. My intent is just to document what the signature would have been. But with Michael adding that it could confuse a casual grepper, I think I'll switch to a standard comment, at minimum. Thanks, --Jacob
Commits
-
Add pg_add_size_overflow() and friends
- 37842f3dc6c2 14.23 landed
- d75b1dc96f0a 15.18 landed
- 924b3e94390d 16.14 landed
- 00e243e6791e 17.10 landed
- c7fb9f765cc5 18.4 landed
- 8934f2136cd8 19 (unreleased) landed
-
postgres: Use pg_{add,mul}_size_overflow()
- e2ceff13d83a 19 (unreleased) landed