Re: Documenting inlining SQL functions

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>

To: Paul Jungwirth <pj@illuminatedcomputing.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-07-19T02:51:49Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Make row compares robust during nbtree array scans.
- bd3f59fdb717 19 (unreleased) cited

On Sunday, July 6, 2025, Paul Jungwirth <pj@illuminatedcomputing.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.