| From: | Ed Behn <ed(at)behn(dot)us> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Persistent data across SETOF calls |
| Date: | 2026-03-21 12:22:38 |
| Message-ID: | CAJBL5DNPYDw84qDohS5CMXOLESsozV7QNJ6NwS1M66+tvHmzdw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Good day-
I maintain the PL/Haskell language handler. Typically, the handler
compiles function code and stores the compiled data in the fn_extra field
of FmgrInfo. The fn_extra field persists from one call to the next within a
query meaning the expensive compilation only needs to happen once per
query.
However, when calling a set-returning function multiple times in a
query, there appears to be no way to carry data from one set to another.
This is because the fn_extra field stores the FuncCallContext structure.
While the user_fctx field of the FuncCallContext structure persists from
one call to the next, it is NULLed out at the end of a set.
For example, if there is a table, t, with a column, i, and a
set-returning function, func, the following query is very inefficient:
SELECT *
FROM t, func(i)
This is because the function is recompiled for each row of t.
Is there a way around this? Ideally, there would be a field that
persists from one set to another within a query.
Thank you for any help you can provide.
-Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Henson Choi | 2026-03-21 12:42:52 | Re: Row pattern recognition |
| Previous Message | Andrew Dunstan | 2026-03-21 12:21:49 | Re: pg_waldump: support decoding of WAL inside tarfile |