Re: The flinfo->fn_extra question, from me this time.

From: Chapman Flack <chap(at)anastigmatix(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: The flinfo->fn_extra question, from me this time.
Date: 2019-06-16 01:46:55
Message-ID: 5D059F8F.6040505@anastigmatix.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/15/19 21:21, Tom Lane wrote:
> Yup. (Of course, you don't have to use the SRF_FIRSTCALL_INIT
> infrastructure.)

That had crossed my mind ... but it seems there's around 80 or 100
lines of good stuff there that'd be a shame to duplicate. If only
init_MultiFuncCall() took an extra void ** argument, and the stock
SRF_FIRSTCALL_INIT passed &(fcinfo->flinfo->fn_extra), seems like
most of it would be reusable. shutdown_MultiFuncCall would need to work
slightly differently, and a caller who wanted to be different would need
a customized variant of SRF_PERCALL_SETUP, but that's two lines.

Cheers,
-Chap

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Steve Singer 2019-06-16 02:05:42 PG 12 beta 1 segfault during analyze
Previous Message Bruce Momjian 2019-06-16 01:28:28 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)