Re: Fixing MSVC's inability to detect elog(ERROR) does not return
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-24T01:47:07Z
Lists: pgsql-hackers
On Thu, 24 Jul 2025 at 12:27, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Hmmm ... but you did check that in fact we can remove such known-dead > code and not get a warning now? Yes. The patch has a small temporary adjustment to BaseBackupGetTargetHandle() to comment out the return. It compiles for me using Visual Studio 2022 without any warnings. If I remove the macro change, I get: [598/2255] Compiling C object src/backend/postgres_lib.a.p/backup_basebackup_target.c.obj src\backend\backup\basebackup_target.c(150) : warning C4715: 'BaseBackupGetTargetHandle': not all control paths return a value David
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