Re: Documenting inlining SQL functions

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Paul Jungwirth <pj(at)illuminatedcomputing(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Documenting inlining SQL functions
Date: 2025-07-19 02:51:49
Message-ID: CAKFQuwYD_vuW42N_+4gFQrsrp7iJN2Kg5rOq8jRAHGWhn32tOA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday, July 6, 2025, Paul Jungwirth <pj(at)illuminatedcomputing(dot)com> wrote:
>
> The second patch adds a new <sect2> explaining how we inline SQL
> functions: both single-result and set-returning. Since this happens
> automatically, it makes a nice progression with the (easy) declarative
> annotations and the (hard) support functions.
>

The fact that attaching a set clause to the function definition (i.e.,
proconfig) prevents inlining is missing from this description.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-07-19 03:08:14 Re: Documenting inlining SQL functions
Previous Message Andres Freund 2025-07-19 02:47:00 Re: index prefetching