Well that's good to know. It was just curious that, in my case, I only saw
this in this particular function.
Anyway. I will consider to handle the memory the same way, if this is the
recommendation.
Many thanks.
/Closed
On Sat, Jul 2, 2016 at 4:45 PM, Tom Lane wrote:
> Dirk Rudolph
tum.") and one of the concatenation results. I’m aware of the MemoryContext being deleted in my case but IMHO builtin functions should be memory safe. (or at least the others I used are).See attached a patch that fixes that against HEAD.Cheers,
Dirk Rudolph | Senior Software EngineerNetcentric
