Re: [HACKERS] WITH RECURSIVE patch V0.1

From: Yoshiyuki Asaba <y-asaba(at)sraoss(dot)co(dot)jp>
To: david(at)fetter(dot)org
Cc: zb(at)cybertec(dot)at, stark(at)enterprisedb(dot)com, ishii(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] WITH RECURSIVE patch V0.1
Date: 2008-05-21 14:34:22
Message-ID: 20080521.233422.1000278277145531989.y-asaba@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Hi,

From: David Fetter <david(at)fetter(dot)org>
Subject: Re: [HACKERS] [PATCHES] WITH RECURSIVE patch V0.1
Date: Mon, 19 May 2008 04:36:30 -0700

> > > 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"?
>
> Couldn't we just have it pay attention to the existing
> max_stack_depth?

Recursive query does not consume stack. The server enters an infinite
loop without consuming stack. Stack-depth error does not happen.

Regards,
--
Yoshiyuki Asaba
y-asaba(at)sraoss(dot)co(dot)jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2008-05-21 15:23:34 Re: [HACKERS] WITH RECURSIVE patch V0.1
Previous Message Merlin Moncure 2008-05-21 13:37:37 Re: idea: storing view source in system catalogs

Browse pgsql-patches by date

  From Date Subject
Next Message Gregory Stark 2008-05-21 15:23:34 Re: [HACKERS] WITH RECURSIVE patch V0.1
Previous Message Magnus Hagander 2008-05-21 14:25:30 Re: libpq Win32 Mutex performance patch