Re: Fixing MSVC's inability to detect elog(ERROR) does not return
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: David Rowley <dgrowleyml@gmail.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2025-09-30T05:24:49Z
Lists: pgsql-hackers
Attachments
- 0001-Rename-pg_builtin_integer_constant_p-to-pg_integer_c.patch (text/plain) patch 0001
On 27.09.25 12:43, David Rowley wrote: > On Wed, 17 Sept 2025 at 15:52, David Rowley <dgrowleyml@gmail.com> wrote: >> Updated patch attached. Thanks for the review. > > Now pushed and awaiting buildfarm feedback. Cool, seems to work. I also tried it on CI by removing a few "silence compiler warning" lines. Quick follow-up: How about we rename pg_builtin_integer_constant_p to pg_integer_constant_p, since it's not actually built-in? See attached patch.
Commits
-
Rename pg_builtin_integer_constant_p to pg_integer_constant_p
- 8e2acda2b098 19 (unreleased) landed
-
Teach MSVC that elog/ereport ERROR doesn't return
- 59c2f03d1ece 19 (unreleased) landed