From: Tom Lane <tgl@sss.pgh.pa.us>
To: kes-kes@yandex.ru
cc: pgsql-docs@lists.postgresql.org
Subject: Re: The document contains false statements
In-reply-to: <175779557876.861.12514976006917547591@wrigleys.postgresql.org>
References: <175779557876.861.12514976006917547591@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Sat, 13 Sep 2025 20:32:58 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <310869.1757805908.1@sss.pgh.pa.us>
Date: Sat, 13 Sep 2025 19:25:08 -0400
Message-ID: <310870.1757805908@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/310870.1757805908%40sss.pgh.pa.us>
Precedence: bulk

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