| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | kes-kes(at)yandex(dot)ru |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: The document contains false statements |
| Date: | 2025-09-13 23:25:08 |
| Message-ID: | 310870.1757805908@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
PG Doc comments form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-09-13 23:26:21 | Re: The document contains false statements |
| Previous Message | David G. Johnston | 2025-09-13 22:59:32 | Re: ANALYZE being a read v write operation clarification |