| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Lifetime of FmgrInfo |
| Date: | 2009-04-17 05:08:58 |
| Message-ID: | 12213.1239944938@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joshua Tolley <eggyknap(at)gmail(dot)com> writes:
> It then does some work to determine whether the result in "function" is
> valid or not. So I got to wondering, what's the lifetime of the
> FunctionCallInfoinfo object passed to the call handler function?
Query lifespan, usually. There are counterexamples on both sides,
but as a rule it's expected that it's worthwhile for a function to
cache anything it can in the fcinfo->flinfo->fn_extra structure.
If it's not worthwhile, that's the caller's fault not the function's.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-04-17 05:27:22 | Re: [PATCH] unalias of ACL_SELECT_FOR_UPDATE |
| Previous Message | KaiGai Kohei | 2009-04-17 04:47:50 | [PATCH] unalias of ACL_SELECT_FOR_UPDATE |