Re: polymorphic arguments and return type for PL/pgSQL - Mailing list pgsql-patches

From Tom Lane
Subject Re: polymorphic arguments and return type for PL/pgSQL
Date
Msg-id 20626.1057017267@sss.pgh.pa.us
Whole thread Raw
In response to Re: polymorphic arguments and return type for PL/pgSQL  (Joe Conway <mail@joeconway.com>)
List pgsql-patches
Joe Conway <mail@joeconway.com> writes:
> With the current linked list, the function is effectively leaked to the
> end of the session anyway, so I don't think this is any worse. Thoughts?

Don't worry about it now.  If a plpgsql function cache entry is
discarded, we leak far more than just the function struct :-( ... and
most of it has been malloc'd, not palloc'd, so it's very hard to get
back.

Someday plpgsql should be rewritten so that it never malloc's anything,
and all its parse data structures are palloc'd into a memory context
associated with the current function cache entry.  Then it would be
practical to recover the memory associated with an obsoleted cache
entry.  But we've lived without this so far, so I guess it's not causing
many people problems.

            regards, tom lane

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Re: [HACKERS] Missing array support
Next
From: Peter Eisentraut
Date:
Subject: Re: Datetime patch