Skip site navigation (1) Skip section navigation (2)

Re: BUG #5982: recursive type crashes postgres

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rikard Pavelic <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5982: recursive type crashes postgres
Date: 2011-04-15 21:06:28
Message-ID: BANLkTin2ud7LiKcKCs-USkXdnKnn2b+SqA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, Apr 15, 2011 at 3:49 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> I haven't seen anything which seems like a reasonable use case yet,
> myself.  If you were *actually* tracking turtles and their
> offspring, that would be a completely worthless data structure.  Is
> there really a case where a reference to the ID of an object of like
> type isn't a better solution?

There are lots of use cases for this.  I use composite types to
marshal data to the client all the time, and recursive structures are
fairly common in many classic problems.  Recursive composites fit the
bill perfectly.

merlin

In response to

Responses

pgsql-bugs by date

Next:From: John R PierceDate: 2011-04-15 21:19:55
Subject: Re: BUG #5982: recursive type crashes postgres
Previous:From: Rikard PavelicDate: 2011-04-15 21:04:03
Subject: Re: BUG #5982: recursive type crashes postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group