| From: | Eugen Konkov <kes-kes(at)yandex(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: The document contains false statements |
| Date: | 2025-09-16 20:55:58 |
| Message-ID: | 1228315805.20250916165558@yandex.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Hello Tom,
Saturday, September 13, 2025, 7:25:08 PM, you wrote:
> 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
Let me continue how to improve this in David G. thread.
--
Best regards,
Eugen Konkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2025-09-16 21:35:19 | Add example for the function with output parameters and RETURN NEXT with no expression |
| Previous Message | PG Doc comments form | 2025-09-15 15:25:22 | Any match distance for large documents can result in search errors |