From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Lakhin <exclusion@gmail.com>
cc: Daniel Verite <daniel@manitou-mail.org>,
        Laurenz Albe <laurenz.albe@cybertec.at>,
        PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
        Robert Haas <robertmhaas@gmail.com>,
        Jakub Wartak <jakub.wartak@enterprisedb.com>
Subject: Re: psql's FETCH_COUNT (cursor) is not being respected for CTEs
In-reply-to: <0023bea5-79c0-476e-96c8-dad599cc3ad8@gmail.com>
References: <10117fba-890b-46ac-9316-cae83108a6a6@manitou-mail.org> <0023bea5-79c0-476e-96c8-dad599cc3ad8@gmail.com>
Comments: In-reply-to Alexander Lakhin <exclusion@gmail.com>
	message dated "Mon, 08 Apr 2024 18:00:00 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <3275589.1712588904.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 08 Apr 2024 11:08:24 -0400
Message-ID: <3275590.1712588904@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/3275590.1712588904%40sss.pgh.pa.us>
Precedence: bulk

Alexander Lakhin <exclusion@gmail.com> writes:
> Now that ExecQueryUsingCursor() is gone, it's not clear, what does
> the following comment mean:?
>  =C2=A0=C2=A0 * We must turn off gexec_flag to avoid infinite recursion.=
=C2=A0 Note that
>  =C2=A0=C2=A0 * this allows ExecQueryUsingCursor to be applied to the in=
dividual query
>  =C2=A0=C2=A0 * results.

Hmm, the point about recursion is still valid isn't it?  I agree the
reference to ExecQueryUsingCursor is obsolete, but I think we need to
reconstruct what this comment is actually talking about.  It's
certainly pretty obscure ...

			regards, tom lane