Re: Large C files

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Large C files
Date: 2011-09-06 07:29:34
Message-ID: 1315294174.29771.1.camel@fsopti579.F-Secure.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On lör, 2011-09-03 at 19:18 -0400, Bruce Momjian wrote:
> FYI, here are all the C files with over 6k lines:
>
> - 45133 ./interfaces/ecpg/preproc/preproc.c
> - 33651 ./backend/parser/gram.c
> - 17551 ./backend/parser/scan.c
> 14209 ./bin/pg_dump/pg_dump.c
> 10590 ./backend/access/transam/xlog.c
> 9764 ./backend/commands/tablecmds.c
> 8681 ./backend/utils/misc/guc.c
> - 7667 ./bin/psql/psqlscan.c
> 7213 ./backend/utils/adt/ruleutils.c
> 6814 ./backend/utils/adt/selfuncs.c
> 6176 ./backend/utils/adt/numeric.c
> 6030 ./pl/plpgsql/src/pl_exec.c
>
> I have dash-marked the files that are computer-generated. It seems
> pg_dump.c and xlog.c should be split into smaller C files.

I was thinking about splitting up plpython.c, but it's not even on that
list. ;-)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yeb Havinga 2011-09-06 08:30:53 Re: [v9.1] sepgsql - userspace access vector cache
Previous Message Peter Eisentraut 2011-09-06 06:20:02 Re: [GENERAL] pg_upgrade problem