Re: [Proposal] Level4 Warnings show many shadow vars
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>,
Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Kyotaro Horiguchi
<horikyota.ntt@gmail.com>, ranier_gyn@hotmail.com,
pgsql-hackers@postgresql.org
Date: 2020-02-27T09:43:50Z
Lists: pgsql-hackers
On 2019-12-18 10:55, Alvaro Herrera wrote: > On 2019-Dec-18, Michael Paquier wrote: > >> Let's take one example. The changes in pg_dump/ like >> /progname/prog_name/ have just been done in haste, without actual >> thoughts about how the problem ought to be fixed. And in this case, >> something which could be more adapted is to remove the argument from >> usage() because progname is a global variable, initialized from the >> beginning in pg_restore. > > We discussed progname as a global/local before -- IIRC in the thread > that introduced the frontend logging API -- and while I think the whole > issue could stand some improvement, we shouldn't let it be driven by > minor changes; that'll only make it more confusing. IMO if we want it > improved, a larger change (involving the bunch of frontend programs) is > what to look for. Maybe what you suggest is an improvement, though > (certainly the "prog_name" patch wasn't). This thread is still in the commit fest, but it's apparently gone as far as it will, so I've set it to "Committed" for lack of a "partial" status. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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