| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: doc: clarify recursion internal behavior |
| Date: | 2022-09-28 17:14:56 |
| Message-ID: | YzSBECSTUbuXL/Jt@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Thu, Sep 8, 2022 at 11:30:04AM -0400, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > On Thu, Sep 8, 2022 at 7:24 AM Peter Eisentraut
> > <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >> On 03.09.22 03:58, Bruce Momjian wrote:
> >>> + While <literal>RECURSIVE</literal> allows queries to be specified
> >>> + recursively, internally all queries are evaluated iteratively.
>
> >> Is that true? Surely there is some recursive behavior in the executor.
>
> > I haven't read the patch, but I think the claim shown here is correct.
>
> I'd be happier if it read "such queries" instead of "all queries".
> The latter is an extremely broad claim, and you have to ignore cases
> like recursive SQL functions in order to even argue it's true.
Done in the attached applied patch.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
| Attachment | Content-Type | Size |
|---|---|---|
| master.diff | text/x-diff | 465 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-09-28 17:15:06 | pgsql: doc: clarify internal behavior of RECURSIVE CTE queries |
| Previous Message | Bruce Momjian | 2022-09-28 17:05:51 | pgsql: revert "warn of SECURITY DEFINER schemas for non-sql_body funcs" |