Re: Guide to PostgreSQL source tree - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Guide to PostgreSQL source tree
Date
Msg-id 25468.998234528@sss.pgh.pa.us
Whole thread Raw
In response to Re: Guide to PostgreSQL source tree  ("Serguei Mokhov" <sa_mokho@alcor.concordia.ca>)
Responses Re: Guide to PostgreSQL source tree
List pgsql-hackers
"Serguei Mokhov" <sa_mokho@alcor.concordia.ca> writes:
> And what's wrong in automated guide generation?

Even more to the point, what's wrong with looking at the source code?
(Why would you want a "line by line" guide if you're not looking at the
source code, anyway?)

We could probably do with more extensive high-level documentation than
we have, to point people to the parts of the code that they need to read
for a particular purpose.  But I agree with Sergei that it's hopeless
to try to divorce low-level documentation from the code itself.

One thing that I find absolutely essential for dealing with any large
project is a full-text indexer (I use Glimpse, but I think there are
others out there).  Being able to quickly look at every use of a
particular identifier goes a long way towards answering questions.
        regards, tom lane


pgsql-hackers by date:

Previous
From: mlw
Date:
Subject: Re: Multiple parameters on aggregates?
Next
From: Peter Eisentraut
Date:
Subject: A fixed user id for the postgres user?