Hi,
That was the question I was facing 5 months ago and trust me I am doing it even now. With an average of 6+ hours going into PostgreSQL Code, even with best practices (as suggested by the developers) I still think I know less than 10 percent. It is too huge to be swallowed at once.
I too had to break it down into pieces and because everything is so interconnected with everything else, it is quite complicated in the beginning. Start with one piece; planner, parser, executor, storage management whatever and slowly it should help you get the bigger picture.
regards,
Vaibhav
I had to break it into
On Fri, Mar 18, 2011 at 3:39 PM, Brendan Jurd
<direvus@gmail.com> wrote:
On 18 March 2011 01:57, hom <
obsidianhom@gmail.com> wrote:
> I try to known how a database is implemented
meaningful help.
I'd emphasise Kevin Grittner's very worthwhile advice. Try to break
your question down into smaller, more specific ones. With a question
like "how does postgres work" you're likely to flounder. But with a
more targeted question, e.g., "what format does postgres use to save
data to disk" or "how does postgres implement ORDER BY", you can make
easier progress, and perhaps you could get more useful pointers from
the people on this list.
Have you read through the "Overview of System Internals" chapter in
the documentation [1]? Perhaps it will help you identify the areas
you wish to explore further, and form more specific questions.
[1] http://www.postgresql.org/docs/current/static/overview.html
Cheers,
BJ