hom <obsidianhom(at)gmail(dot)com> wrote:
> I try to known how a database is implemented and I have been
> reading PG source codes for a month.
find -name '*.h' -or -name '*.c' \
| egrep -v '^\./src/test/.+/tmp_check/' \
| xargs cat | wc -l
Depending on how you do the math, that's about 50,000 lines of code
per day to get through it in the time you mention.
> Is there any article or some way could help understand the source
> code ?
Your best bet would be to follow links from the Developers tab on
the main PostgreSQL web site:
In particular the Developer FAQ page:
And the "Coding" links:
Before reading code in a directory, be sure to read any README
file(s) in that directory carefully.
It helps to read this list.
In spite of reviewing all of that myself, it was rather intimidating
when I went to work on a major patch 14 months ago. Robert Haas
offered some good advice which served me well in that effort --
divide the effort in to a series of incremental steps, each of which
deals with a small enough portion of the code to get your head
around. As you work in any one narrow area, it becomes increasingly
clear; with that as a base you can expand your scope.
When you're working in the code, it is tremendously helpful to use
an editor with ctags support (or similar IDE functionality).
I hope this is helpful. Good luck.
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2011-03-17 16:17:22|
|Subject: Re: Re: [COMMITTERS] pgsql: Basic Recovery Control
functions for use in Hot Standby. Pause,|
|Previous:||From: Bruce Momjian||Date: 2011-03-17 15:22:12|
|Subject: Re: I am confused after reading codes of PostgreSQL