Re: Cleanup shadows variable warnings, round 1

Álvaro Herrera <alvherre@kurilemu.de>

From: Álvaro Herrera <alvherre@kurilemu.de>
To: Chao Li <li.evan.chao@gmail.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>, Peter Eisentraut <peter@eisentraut.org>, Peter Smith <smithpb2250@gmail.com>
Date: 2026-03-03T12:12:38Z
Lists: pgsql-hackers
On 2026-Mar-03, Chao Li wrote:

> > On Mar 3, 2026, at 18:26, Álvaro Herrera <alvherre@kurilemu.de> wrote:
> > 
> > Pushed 0001.
> 
> Hi Alvaro, thank you very much for pushing 0001. But I don’t see it. I
> tried to pull master and refresh
> https://git.postgresql.org/cgit/postgresql.git/log/?qt=grep&q=, none
> of them shows 0001 pushed.

Oh, pager decided to intervene and hang the whole thing.  Done now.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix new-to-v19 -Wshadow warnings

  2. Reduce scope of for-loop-local variables to avoid shadowing

  3. Fix local-variable shadowing in pg_trgm's printSourceNFA().