Re: Tree structure index usage - Mailing list pgsql-sql

From Josh Berkus
Subject Re: Tree structure index usage
Date
Msg-id web-539545@davinci.ethosmedia.com
Whole thread Raw
In response to Tree structure index usage  ("Aasmund Midttun Godal" <postgresql@envisity.com>)
List pgsql-sql
Aasmund,

> CREATE TABLE my_tree (
>  id SERIAL PRIMARY KEY,
>  dir INTEGER references my_tree ON DELETE CASCADE ON UPDATE CASCADE,
>  name TEXT,
>  UNIQUE(name, dir)
> );
> 
> Then I have a function is_parent(integer, integer), it will tell you
> if the second integer (id) is a sub directory of the first
> (regardless of the number of levels).
> 
> now obviously is_parent  does some queries itself.
> 
> and someone may choose to update the dir value of a row.
> 
> is there any way I can create an efficient index on this
> structure/function?

Hmmm.  Seperate indexes on ID and DIR should be sufficient for most
purposes.  More complex approaches are only likely to slow things down.
How many records do you have?  How many levels to the tree structure?

For an excellent discussion of efficient construction and queryin of
tree structures, see Joe Celko's "SQL for Smarties."

-Josh

______AGLIO DATABASE SOLUTIONS___________________________                                      Josh Berkus Complete
informationtechnology      josh@agliodbs.com  and data management solutions       (415) 565-7293 for law firms, small
businesses       fax 621-2533   and non-profit organizations.      San Francisco
 


pgsql-sql by date:

Previous
From: caldodge@fpcc.net (Calvin Dodge)
Date:
Subject: Re: PostgreSQL SELECT error
Next
From: "Aasmund Midttun Godal"
Date:
Subject: to_char adds leading space, intended?