| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
| 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 20:31:48 |
| Message-ID: | aR96tFMuKO9RDYQF@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 20, 2025 at 04:49:51PM +0300, Aleksander Alekseev wrote:
> Hi,
>
> > > While working on a talk, I studied the number of code line changes in
> > > each major release, and found PG 17 surprisingly reduced code line count
> > > by 10%. To get the code line count, I used /pgtop/src/tools/codelines,
> > > which runs:
> >
> > [..]
> > Overall, there is a 4% increase according to this tool. What is
> > convenient about `cloc` - you can count only what you want, e.g. code
> > without comments, etc.
>
> Oops, I didn't notice that you were comparing PG16 and PG17. Still,
> the result with `cloc` is similar, +4% approximately. Apologies for
> the noise.
Yes, that is another discussion we can have --- whether line count alone
is what we want.
--
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2025-11-20 20:34:30 | Re: Issue with logical replication slot during switchover |
| Previous Message | Bruce Momjian | 2025-11-20 20:30:15 | Re: 10% drop in code line count in PG 17 |