| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Adriano Lange <adriano(at)c3sl(dot)ufpr(dot)br>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com> |
| Subject: | Re: graph representation of data structures in optimizer |
| Date: | 2009-02-19 20:33:40 |
| Message-ID: | 200902192233.41370.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday 19 February 2009 22:17:54 Adriano Lange wrote:
> Tom Lane escreveu:
> > But really I think the problem with this approach is that the
> > information density is too low --- imagine what it would look like in a
> > six-or-more-way join. I don't think the graphical approach is helpful
> > at all here.
>
> I was thinking about the hard visualization and navigability in the
> graph. I think that a good solution for this would be a dynamic
> navigability in their nodes and a rearrange their positions by focused
> node. I'm not remembering now, but I've saw a tool like this.
http://prefuse.org could be useful for that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-02-19 20:39:56 | Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
| Previous Message | Heikki Linnakangas | 2009-02-19 20:28:31 | Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |