Re: Cleanup shadows variable warnings, round 1 - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: Cleanup shadows variable warnings, round 1
Date
Msg-id 202603031015.s6lmrgi7x67r@alvherre.pgsql
Whole thread Raw
In response to Re: Cleanup shadows variable warnings, round 1  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: Cleanup shadows variable warnings, round 1
Re: Cleanup shadows variable warnings, round 1
List pgsql-hackers
Pushed 0001.

Three things about the next ones,

1. if you rename a function argument, then the function declaration
should match the new name as well.

2. xlogrecovery.c has far too many global variables.  Can we use this
opportunity to try to get rid of some of them?  Especially one called
"xlogreader" is I think quite bug-prone.

3. I disagree with some of the choices made; for instance rather than
rename the local "progname" variables in all those places, I would
rename the global to logging_progname in logging.c; in bringetbitmap
(0002) I would rename the outer "tmp" to "sizecheck" or something like
that.  I guess this is mostly matter of mostly arbitrary judgment ...

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Fix slotsync worker busy loop causing repeated log messages
Next
From: Lukas Fittl
Date:
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?