Tom Lane wrote:
>> The memory management of the init functions looks weird. In spell.c,
>> there's this piece of code:
>
> I saw that and didn't care for it much, but didn't look into exactly
> what would be needed to get rid of it. (I did clean up another place
> that had a *global* magic context pointer ... that looked like trouble
> waiting to happen.) If you make the outside caller create the context,
> does it need to be passed explicitly or can it just be
> CurrentMemoryContext when they are called?
I believe CurrentMemoryContext would work just fine. I'll put together a
patch.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com