From: Jim C. Nasby <jnasby@pervasive.com>
To: Gnanavel S <s.gnanavel@gmail.com>
Cc: Jonah H. Harris <jonah.harris@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: PostgreSQL overall design
Date: Fri, 30 Sep 2005 18:19:08 -0500
Message-ID: <20050930231908.GP40138@pervasive.com> (raw)
In-Reply-To: <eec3b03c05092706305605868a@mail.gmail.com>
References: <eec3b03c0509270250bc2fc97@mail.gmail.com>
<20050927102701.GE1784@penne.toroid.org>
<36e682920509270600439cfc4a@mail.gmail.com>
<eec3b03c05092706305605868a@mail.gmail.com>
On Tue, Sep 27, 2005 at 07:00:14PM +0530, Gnanavel S wrote:
> On 9/27/05, Jonah H. Harris <jonah.harris@gmail.com> wrote:
> >
> > Were you looking for a call graph?
>
>
> Yes. I want to know the list and sequence of files involved during a call.
Total non-coder question, but is there an open-source utility that's
capable of generating that? Seems like a useful piece of documentation
to have. Also seems like it'd be completely impractical to maintain by
hand.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jnasby@pervasive.com, s.gnanavel@gmail.com, jonah.harris@gmail.com, pgsql-hackers@postgresql.org
Subject: Re: PostgreSQL overall design
In-Reply-To: <20050930231908.GP40138@pervasive.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox