Skip site navigation (1) Skip section navigation (2)

Re: I am confused after reading codes of PostgreSQL three week

From: hom <obsidianhom(at)gmail(dot)com>
To: Vaibhav Kaushal <vaibhavkaushal123(at)gmail(dot)com>
Cc: Brendan Jurd <direvus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: I am confused after reading codes of PostgreSQL three week
Date: 2011-03-18 14:44:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
2011/3/18 Vaibhav Kaushal <vaibhavkaushal123(at)gmail(dot)com>:
> 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

Thanks Vaibhav .
I have step into parser before but I meet a problem:

when I debug step in the scanner_init(),  Eclipse always finds scan.l
and the excute order is not match the file.
I think it should be scan.c actually but I don't known how to trace
into scan.c :(
PS: I have turn "Search for duplicate source files" option on.

I have posted to the mail list, but it have not solved.

here is the link:

Best Wishes!


In response to


pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-03-18 14:52:13
Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Previous:From: Thom BrownDate: 2011-03-18 14:41:51
Subject: Re: [COMMITTERS] pgsql: Fix various possible problems with synchronous replication.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group