From: | Werachart Jantarataeme <wjt(at)ziif(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | How to do the modular test |
Date: | 2001-04-15 07:05:16 |
Message-ID: | Pine.LNX.4.21.0104151404520.1163-100000@mail.phl.co.th |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi pgsql-hackers,
Could anyone advise me how to do modular test in any partial
PostgreSQL's modules?
I am interested in the PostgreSQL development. I have begun study the
DBMS source code by developer documentation provided by postgresql.org
especially internal.ps that is the best explaination for developer
beginner, I think.
Moreover, the RedHat SourceNavigator I have found, is a great tools for
me. Without it, I might not able to get more understanding of the
PostgreSQL source code.
Now I am concentrating on the Executor module. I plan to create a new
Join Executor let's say ParallelJoin to enhance the Join operator
processing. As this moment, I may use the HybridJoin algorithm
implementing in the HashJoin module as my guidance but the NestLoop and
MergeJoin may be considered in the furture.
What I would like to know is, if I have changed some ot the modules,
how can I use GNU gdb to debug the modified codes?
I am sorry if the question is disturb your mailing list. I know this is
not the issue related in your TODO list. However I have expected to your
response.
thanks and regards,
Werachart.
From | Date | Subject | |
---|---|---|---|
Next Message | Mario Weilguni | 2001-04-15 08:42:19 | Re: NUMERIC type benchmarks |
Previous Message | Nathan Myers | 2001-04-15 06:47:38 | Re: Fast Forward (fwd) |