| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 10% drop in code line count in PG 17 |
| Date: | 2025-11-20 21:15:04 |
| Message-ID: | 98C089B8-6827-4E06-84CA-858DCCB15103@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 20 Nov 2025, at 21:30, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> 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.
Right, but that was sort of my point, you are counting lines which aren't part
of the cluster install since src/test has lot's of C code which is just tests.
$ find src/test/ -name '*.[chyl]' | xargs cat|wc -l
23587
And the cluster install does contain C++ which isn't counted for.
$ find . -name '*.cpp' | xargs cat|wc -l
1485
Counting just lines in a cluster install is a valid use case but the script
might need some adaptations to match the current tree.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-11-20 21:16:23 | Re: another autovacuum scheduling thread |
| Previous Message | Peter Smith | 2025-11-20 21:08:58 | Re: CREATE/ALTER PUBLICATION improvements for syntax synopsis |