Re: Adjacency Lists vs Nested Sets

From: Michael Glaesemann <grzm(at)seespotcode(dot)net>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Matthew Hixson <hixson(at)poindextrose(dot)org>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Adjacency Lists vs Nested Sets
Date: 2007-07-10 19:25:07
Message-ID: BF2AA5AF-D551-43F9-A44B-CC179D05F179@seespotcode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Jul 10, 2007, at 13:51 , Richard Huxton wrote:

> Matthew Hixson wrote:
>> Does Postgres have any native support for hierarchical data
>> storage? I'm familiar with the Adjacency List technique, but am
>> trying to determine whether or not Nested Sets would make sense
>> for our application or not. I understand that Nested Sets might
>> be better for high read applications, but write heavy applications
>> suffer from poor performance.
>
> You might find the "ltree" add-on in contrib useful. Look in the
> "contrib" directory of your source installation, or the addons/
> extras package of your distribution.

And as for performance, do remember to benchmark your app using the
different techniques. Adjacency lists have their own performance
issues as well. It definitely depends on your app.

Michael Glaesemann
grzm seespotcode net

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Harpreet Dhaliwal 2007-07-10 19:33:34 Re: Duplicate Unique Key constraint error
Previous Message Tom Lane 2007-07-10 19:09:14 Re: Duplicate Unique Key constraint error