Re: [COMMITTERS] pgsql: Clean up the #include mess a little. - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [COMMITTERS] pgsql: Clean up the #include mess a little.
Date
Msg-id 20120815223040.GS25473@momjian.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Clean up the #include mess a little.  (Ants Aasma <ants.aasma@eesti.ee>)
Responses Re: [COMMITTERS] pgsql: Clean up the #include mess a little.
List pgsql-hackers
On Wed, Sep  7, 2011 at 01:20:17AM +0300, Ants Aasma wrote:
> On Tue, Sep 6, 2011 at 10:18 PM, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:
> > I wonder what happens if files in the same subdir are grouped in a
> > subgraph.  Is that possible?
> 
> Possible, and done. Also added possivility to add .c files to the graph,
> coloring by subdir and possibility exclude nodes from the graph. I didn't yet
> bother to clean up the code - to avoid eye damage, don't look at the source.
> 
> Bad news is that it doesn't significantly help readability for the all nodes
> case. See all_with_subgraphs.svgz.  It does help for other cases.
> For example parsenodes.h.svgz has the result for
> render_includes.py --select='nodes/parsenodes.h+*-*' --subgraphs
> and execnodes.h.svgz for
> --subgraphs --select='nodes/execnodes.h+*-*'

Should we add this script and instructions to src/tools/pginclude?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Planner avoidance of index only scans for partial indexes
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #6184: Inconsistencies in log messages