Re: Query Plan Columns

From: David Fetter <david(at)fetter(dot)org>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Query Plan Columns
Date: 2010-11-06 17:17:05
Message-ID: 20101106171705.GD5451@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 05, 2010 at 01:39:07PM -0700, Josh Berkus wrote:
>
> > Of course, there are containers too, which are not in your list at all.
> > How do you intend to represent the tree-ish structure in a flat table?
>
> Andrew: we'll use a proximity tree.

Adjacency list?

If so, in my experience, it's best to separate the node descriptions
from the adjacency list that links them together.

Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-11-06 17:34:46 IA64 versus effective stack limit
Previous Message Robert Haas 2010-11-06 17:09:49 Re: temporary functions (and other object types)