Date: Tue, 16 Sep 2025 16:55:58 -0400
From: Eugen Konkov <kes-kes@yandex.ru>
Message-ID: <1228315805.20250916165558@yandex.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: pgsql-docs@lists.postgresql.org
Subject: Re: The document contains false statements
In-Reply-To: <310870.1757805908@sss.pgh.pa.us>
References: <175779557876.861.12514976006917547591@wrigleys.postgresql.org>
 <310870.1757805908@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/1228315805.20250916165558%40yandex.ru>
Precedence: bulk

Hello Tom,

Saturday, September 13, 2025, 7:25:08 PM, you wrote:

> PG Doc comments form <noreply@postgresql.org> writes:
>> The following documentation comment has been logged on the website:
>> Page: https://www.postgresql.org/docs/17/sql-createfunction.html
>> Description:

>>> This is effectively another way of declaring a named OUT parameter

>> Actually OUT works twice slower in compare to RETURNS TABLE

> You stopped reading halfway through that sentence... it says

>     This is effectively another way of declaring a named OUT parameter,
>     except that RETURNS TABLE also implies RETURNS SETOF.

> The difference between a set-returning and not-set-returning
> function might explain what you're seeing, particularly because
> the rules for inlining SQL functions are different in the two
> cases.

> A documentation comment is not the place to pursue this further,
> but you could ask for help on our pgsql-performance mailing list.

>                         regards, tom lane

Let me continue how to improve this in David G. thread.

-- 
Best regards,
Eugen Konkov