Message-ID: <0023bea5-79c0-476e-96c8-dad599cc3ad8@gmail.com>
Date: Mon, 8 Apr 2024 18:00:00 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.2
Subject: Re: psql's FETCH_COUNT (cursor) is not being respected for CTEs
Content-Language: en-US
To: Daniel Verite <daniel@manitou-mail.org>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
 PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
 Robert Haas <robertmhaas@gmail.com>,
 Jakub Wartak <jakub.wartak@enterprisedb.com>
References: <10117fba-890b-46ac-9316-cae83108a6a6@manitou-mail.org>
From: Alexander Lakhin <exclusion@gmail.com>
In-Reply-To: <10117fba-890b-46ac-9316-cae83108a6a6@manitou-mail.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/0023bea5-79c0-476e-96c8-dad599cc3ad8%40gmail.com>
Precedence: bulk

Hello Daniel and Tom,

08.04.2024 17:25, Daniel Verite wrote:
>
>> So I whacked the patch around till I liked it better, and pushed it.
> Thanks for taking care of this!

Now that ExecQueryUsingCursor() is gone, it's not clear, what does
the following comment mean:?
    * We must turn off gexec_flag to avoid infinite recursion.  Note that
    * this allows ExecQueryUsingCursor to be applied to the individual query
    * results.

Shouldn't it be removed?

Best regards,
Alexander