Re: 10% drop in code line count in PG 17

On 2025-Nov-20, David Rowley wrote:

> 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

Maybe this should also consider .pl and .pm files ... we now have almost
90k lines of Perl code in branch master:

I perhan: master 0 0$ git ls-files -- '*.pl' | xargs cat | wc -l
77234
C perhan: master 0 0 0$ git ls-files -- '*.pm' | xargs cat | wc -l
10386

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"After a quick R of TFM, all I can say is HOLY CR** THAT IS COOL! PostgreSQL was
amazing when I first started using it at 7.2, and I'm continually astounded by
learning new features and techniques made available by the continuing work of
the development team."
Berend Tober, http://archives.postgresql.org/pgsql-hackers/2007-08/msg01009.php