From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-committers <pgsql-committers@lists.postgresql.org>
Subject: Re: pgsql: doc: clarify recursion internal behavior
Date: Thu, 08 Sep 2022 11:30:04 -0400
Message-ID: <3976627.1662651004@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+TgmoYHkORN2LtHUW3Sp3=aGYiJE3m8ExSL_FOU3LUHb9BjRQ@mail.gmail.com>
References: <E1oUIQF-001AWC-Dh@gemulon.postgresql.org>
<f88a4e74-8cb2-0f0f-622f-6bcff0c17ec4@enterprisedb.com>
<CA+TgmoYHkORN2LtHUW3Sp3=aGYiJE3m8ExSL_FOU3LUHb9BjRQ@mail.gmail.com>
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Sep 8, 2022 at 7:24 AM Peter Eisentraut
> <peter.eisentraut@enterprisedb.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.
regards, tom lane
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-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, peter.eisentraut@enterprisedb.com, bruce@momjian.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: doc: clarify recursion internal behavior
In-Reply-To: <3976627.1662651004@sss.pgh.pa.us>
* 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