Re: return MAX and when it happened - Mailing list pgsql-general

From Scara Maccai
Subject Re: return MAX and when it happened
Date
Msg-id 49249BE6.3050700@yahoo.it
Whole thread Raw
In response to Re: return MAX and when it happened  (Sam Mason <sam@samason.me.uk>)
Responses Re: return MAX and when it happened
List pgsql-general
Sam Mason wrote:
> The custom aggregate sounds the
> most elegant, it's just annoying that it's so much fiddling to get it
> all working to start with
Thanks.

I think I wrote it, but there's something I don't get from the docs: do
I have to call

get_call_result_type(fcinfo, NULL, &tupdesc)

every time?

I mean: the only example I've found about returning Composite Types
talks about returning sets as well (34.9.10. Returning Sets). In that
example the get_call_result_type call is done once:

if (SRF_IS_FIRSTCALL())
{
  [...]
  if (get_call_result_type(fcinfo, NULL, &tupdesc) != TYPEFUNC_COMPOSITE)
  [...]
}


Should I do something like that in my function or that only applies to
function returning sets?
I'm calling it every time now but I don't know if it's right...




pgsql-general by date:

Previous
From: Howard Cole
Date:
Subject: Re: How to reduce impact of a query.
Next
From: "Koichi Suzuki"
Date:
Subject: Re: lesslog "incorrect resource manager data checksum."