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

On Thu, Nov 20, 2025 at 03:30:15PM -0500, Bruce Momjian wrote:
> On Thu, Nov 20, 2025 at 10:38:49AM +0100, Daniel Gustafsson wrote:
> > > On 19 Nov 2025, at 20:59, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > > While working on a talk, I studied the number of code line changes in
> > > each major release,
> >
> > This script will only pick up C, but will pick up C in src/test but not any
> > Perl code using the C modules in src/test etc. These days we also have C++ and
> > some Python in the tree. Maybe it's time to revise it for todays codebase
> > which is quite different from when it was written 20 years ago?
>
> Yeah, that's part of a larger discussion. In an email I just sent I
> suggested we are trying to count files that are part of a cluster
> install, rather than testing files, but again, needs discussion.

Actually, another discussion would be why we have src/tools/codelines in
the git tree at all. I added it in 2005 to use in counting code lines,
and I thought we could consider it our standard method, but I am not
sure anyone aside from me even uses it, and it is clear there are
multiple methods people consider valid. Should we just remove it?

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.