2010/10/10 Vaibhav Kaushal <vaibhavkaushal123@gmail.com>:
> Thanks for the reply.
> So if I am not wrong, I will have to understand the whole querying process
> in detail? If it is so, then where do I start from?
> -Vaibhav
>
> On Sun, Oct 10, 2010 at 1:41 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
>>
>> On sön, 2010-10-10 at 13:32 +0530, Vaibhav Kaushal wrote:
>> > I have gone through the source code a bit but I wanted to know that
>> > which file contains the code that performs the final SLECTION after
>> > the optimizer has created the final plan? I mean which part of the
>> > executor is responsible for the SELCT to be run?
>>
>> That depends on what plan was chosen for the SELECT, since the executor
>> is primarily organized by plan node type, independent of which statement
>> caused the plan to be generated.
>>
> So if I am not wrong, I will have to understand the whole querying process
> in detail? If it is so, then where do I start from?
>
And it depends on what you are interested in. If the executor behavior
is your interest, see execMain.c, but your question looks more
interested in nodeSeqscan.c which scans rows from a relation.
Regards,
--
Hitoshi Harada