pg.ddx.io  pgsql-patches@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Fetter <david@fetter.org>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: pgsql-patches@postgresql.org
Cc: pgsql-hackers@postgresql.org
Cc: y-asaba@sraoss.co.jp
Subject: Re: [PATCHES] WITH RECUSIVE patches 0717
Date: Fri, 18 Jul 2008 08:13:08 -0700
Message-ID: <20080718151308.GT28307@fetter.org> (raw)
In-Reply-To: <20080718145608.GS28307@fetter.org>
References: <20080717.184025.85407905.t-ishii@sraoss.co.jp>
	<20080717160115.GE28307@fetter.org>
	<20080718.104120.08328518.t-ishii@sraoss.co.jp>
	<20080718145608.GS28307@fetter.org>

On Fri, Jul 18, 2008 at 07:56:09AM -0700, David Fetter wrote:
> On Fri, Jul 18, 2008 at 10:41:20AM +0900, Tatsuo Ishii wrote:
> > > > Here is the lastest WITH RECURSIVE patches against CVS HEAD created by
> > > > Yoshiyuki Asaba and minor corrections by Tatsuo Ishii.
> > > 
> > > I tried this patch vs. CVS HEAD used my usual configure option with
> > > only --with-prefix set, then tried to make, and got:
> > > 
> > > make[3]: *** No rule to make target `parse_cte.o', needed by `objfiles.txt'.  Stop.
> > > make[3]: Leaving directory `/home/shackle/pgsql/src/backend/parser'
> > > make[2]: *** [parser-recursive] Error 2
> > > make[2]: Leaving directory `/home/shackle/pgsql/src/backend'
> > > make[1]: *** [all] Error 2
> > > make[1]: Leaving directory `/home/shackle/pgsql/src'
> > > make: *** [all] Error 2
> > > 
> > > Is there something missing?
> > 
> > Oops. I forgot to include patches against newly added files. Please
> > try included patches.
> 
> This now compiles.
> 
> I have a test case that hangs and smashes.
> 
> WITH t(i) AS (
>     SELECT * FROM generate_series(1,5)
> )
> SELECT
>     t1.i,
>     2*t2.i
> FROM
>     t AS t1
> JOIN
>     t AS t2 USING(i);
> 
> server closed the connection unexpectedly
>     This probably means the server terminated abnormally
>     before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
> 
> An equivalent query without RECURSIVE breaks in a different, in some
> sense even more severe, way, as in it just hands out a wrong result
> set:

D'oh!  That's what I get for sending this before waking up.  It works
just fine.

> While this case is trivial, others are not.  For example, if someone
> wishes to do a k-deep summary on a parts explosion n levels deep,
> n>k, one way to do this would be to JOIN the k-deep part of the path
> enumeration to the parts greater than k deep.
> 
> What would need to be fixed in order to make the above things work?

Cheers,
David.
-- 
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate



view thread (11+ messages)  latest in thread

Message-ID: <20080718151308.GT28307@fetter.org>
Permalink:  ../20080718151308.GT28307@fetter.org/
Also on:    postgresql.org/message-id/20080718151308.GT28307@fetter.org

 · 

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-patches@postgresql.org
  Cc: david@fetter.org, ishii@postgresql.org, pgsql-hackers@postgresql.org, y-asaba@sraoss.co.jp
  Subject: Re: [PATCHES] WITH RECUSIVE patches 0717
  In-Reply-To: <20080718151308.GT28307@fetter.org>

* 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