Re: 10% drop in code line count in PG 17
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Date: 2025-11-19T23:23:25Z
Lists: pgsql-hackers
On Thu, 20 Nov 2025 at 10:58, Bruce Momjian <bruce@momjian.us> wrote: > I think you are right. Attached is the difference between the output > for 16 & 17. Let me do some more research and run all the versions > again and report back, thanks. Maybe you'd be better with git ls-files if you only want just what's in the repo. Something like: for b in "REL8_0_0" "REL8_1_0" "REL8_2_0" "REL8_3_0" "REL8_4_0" "REL9_0_0" "REL9_1_0" "REL9_2_0" "REL9_3_0" "REL9_4_0" "REL9_5_0" "REL9_6_0" "REL_10_0" "REL_11_0" "REL_12_0" "REL_13_0" "REL_14_0" "REL_15_0" "REL_16_0" "REL_17_0" "REL_18_0" "master"; do git checkout -f $b > /dev/null 2>&1 && echo -n "$b " && git ls-files -- '*.[chyl]' | xargs cat | wc -l; done Careful with the git checkout "-f" though. David