Re: [Proposal] Level4 Warnings show many shadow vars
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Robert Haas <robertmhaas@gmail.com>,
Ranier Vilela <ranier_gyn@hotmail.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2019-12-09T21:38:04Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On 2019-12-09 11:59:23 -0500, Robert Haas wrote: >> On Mon, Dec 9, 2019 at 11:48 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> The only thing I think is really a substantial bug risk here is your >>> point about our own macros referencing our own global variables. >>> We might be better off fixing that in a localized way by establishing >>> a policy that any such macros should be converted to static inlines. >> That would be a lot of work, but it would probably have some side >> benefits, like making things more type-safe. > It's also not always possible in C99, as we have plenty macros with > essentially dynamic types. And there's no typeof() in standard C, > unfortunately (C11's _Generic can help, but isn't great either). How much overlap is there between macros referencing global variables and macros with indeterminate types? Not much I bet. I'd mostly be worried about things like CHECK_FOR_INTERRUPTS(). regards, tom lane
Commits
-
Remove shadow variables linked to RedoRecPtr in xlog.c
- 668365014d7b 11.7 landed
- 35c01529b8c9 12.2 landed
- 70116493a8e0 13.0 landed
-
Fix calculation for WAL segment recycling and removal
- d9fadbf13103 12.0 cited