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


From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: david(at)fetter(dot)org
Cc: ishii(at)postgresql(dot)org, y-asaba(at)sraoss(dot)co(dot)jp, postgres(at)cybertec(dot)at,pgsql-patches(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] WITH RECURSIVE updated to CVS TIP
Date: 2008-07-16 00:37:25
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
> On Tue, Jul 08, 2008 at 06:01:05PM +0900, Tatsuo Ishii wrote:
> > Here is the patches he made against CVS HEAD (as of today).
> > 
> > According to him followings are fixed with the patches:
> > 
> > - fix crush with DISTINCT
> > - fix creating VIEW
> > - fix the case when recursion plan has another recursion plan under it
> > - fix WITH RECURSIVE ...(..) SELECT ...WHERE.. returns wrong result
> > - fix inifinit recursion with OUTER JOIN
> Great!
> I've patched psql for some partial support of WITH [RECURSIVE].

Thanks. I will incorporate them with propsed patches.

> > Not yet fixed:
> > 
> > - detect certain queries those are not valid acroding to the standard
> > - sort query names acording to the dependency
> Is there something in the standard on how to do this?  How to sort the
> nodes other ways?

No idea. What do you think if we allow only one query name at the
moment. I guess most WITH RECURISVE use cases are enough with single
query name.
Tatsuo Ishii
SRA OSS, Inc. Japan

In response to


pgsql-hackers by date

Next:From: David E. WheelerDate: 2008-07-16 00:45:00
Subject: Re: PATCH: CITEXT 2.0 v3
Previous:From: Xiao MengDate: 2008-07-16 00:23:31
Subject: gsoc, store hash index tuple with hash code only

pgsql-patches by date

Next:From: Bruce MomjianDate: 2008-07-16 00:49:35
Subject: Re: array_fill function
Previous:From: Tom LaneDate: 2008-07-15 14:56:55
Subject: Re: [PATCHES] WIP: executor_hook for pg_stat_statements

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