From: | Yoshiyuki Asaba <y-asaba(at)sraoss(dot)co(dot)jp> |
---|---|
To: | zb(at)cybertec(dot)at |
Cc: | stark(at)enterprisedb(dot)com, ishii(at)postgresql(dot)org, david(at)fetter(dot)org, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: WITH RECURSIVE patch V0.1 |
Date: | 2008-05-19 08:57:17 |
Message-ID: | 20080519.175717.468378203492531856.y-asaba@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Hi,
From: Zoltan Boszormenyi <zb(at)cybertec(dot)at>
Subject: Re: [PATCHES] WITH RECURSIVE patch V0.1
Date: Mon, 19 May 2008 08:19:17 +0200
> >> Also, it seems there are no infinite recursion detection:
> >>
> >> # with recursive x(level, parent, child) as (
> >> select 1::integer, * from test_connect_by where parent is null
> >> union all
> >> select x.level + 1, base.* from test_connect_by as base, x where base.child
> >> = x.child
> >> ) select * from x;
> >> ... it waits and waits and waits ...
> >>
> >
> > Well, psql might wait and wait but it's actually receiving rows. A cleverer
> > client should be able to deal with infinite streams of records.
> >
>
> I think it's the other way around. The server should not emit infinite
> number of records.
How about adding new GUC parameter "max_recursive_call"?
Regards,
--
Yoshiyuki Asaba
y-asaba(at)sraoss(dot)co(dot)jp
From | Date | Subject | |
---|---|---|---|
Next Message | Zoltan Boszormenyi | 2008-05-19 09:10:30 | Re: WITH RECURSIVE patch V0.1 |
Previous Message | Martijn van Oosterhout | 2008-05-19 08:42:23 | Re: [HACKERS] WITH RECURSIVE patch V0.1 |
From | Date | Subject | |
---|---|---|---|
Next Message | Zoltan Boszormenyi | 2008-05-19 09:10:30 | Re: WITH RECURSIVE patch V0.1 |
Previous Message | Martijn van Oosterhout | 2008-05-19 08:42:23 | Re: [HACKERS] WITH RECURSIVE patch V0.1 |