pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Andrew Rawnsley <ronz@ravensfield.com>
To: Qing Zhao <qzhao@quotefx.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: column size too large, is this a bug?
Date: Sun, 28 Mar 2004 11:25:41 -0800
Message-ID: <200403281125.41590.josh@agliodbs.com> (raw)
In-Reply-To: <8B3A05B5-7F51-11D8-93F3-000393A47FCC@ravensfield.com>
References: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net>
	<1DA4E1C7-7F4B-11D8-8D3D-000A95AB8896@quotefx.net>
	<8B3A05B5-7F51-11D8-93F3-000393A47FCC@ravensfield.com>

Andrew,

> I used to use the connect-by patch, but have since rewritten everything
> to use a nested set model. 

Cool!   You're probably the only person I know other than me using nested sets 
in a production environment.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (22+ messages)  latest in thread

Message-ID: <200403281125.41590.josh@agliodbs.com>
Permalink:  ../200403281125.41590.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200403281125.41590.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, ronz@ravensfield.com, qzhao@quotefx.net, tgl@sss.pgh.pa.us, sszabo@megazone.bigpanda.com
  Subject: Re: column size too large, is this a bug?
  In-Reply-To: <200403281125.41590.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