pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Robert Treat <xzilla@users.sourceforge.net>
To: Andrew Rawnsley <ronz@ravensfield.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Nested Sets WAS: column size too large, is this a bug?
Date: Tue, 30 Mar 2004 08:38:50 -0800
Message-ID: <200403300838.50538.josh@agliodbs.com> (raw)
In-Reply-To: <200403300920.27739.xzilla@users.sourceforge.net>
References: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net>
	<200403281125.41590.josh@agliodbs.com>
	<200403300920.27739.xzilla@users.sourceforge.net>

Robert,

> If you search the pgsql-sql archives you'll find some helpful threads on
> using nested sets in PostgreSQL, one in particular I  was involved with was
> a generic "move_tree" function that enabled moving a node from one branch
> to another.

I have to admit to failing to follow -SQL over the last few months.    This 
list and Hackers are pretty much the only ones I read all of.

Maybe I should get back on -SQL and we can compare move_tree functions :-)  

Did yours use a temp table, or some other means?

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (3+ messages)  latest in thread

Message-ID: <200403300838.50538.josh@agliodbs.com>
Permalink:  ../200403300838.50538.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200403300838.50538.josh@agliodbs.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com, xzilla@users.sourceforge.net, ronz@ravensfield.com
  Subject: Re: Nested Sets WAS: column size too large, is this a bug?
  In-Reply-To: <200403300838.50538.josh@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox