On Thu, Jul 21, 2016 at 4:09 PM, happy times <guangzhouzhang(at)qq(dot)com> wrote:
> My question: Is this problem as-designed?
>
Actually problem is in exec_stmt_dynexecute function, We make a copy of the
query string,
and before we free it, it thow an error from SPI_execute (because table
does not exist)
And this is happening in infinite loop, so we are seeing memory leak.
exec_stmt_dynexecute
{
....
/* copy it out of the temporary context before we clean up */
querystr = pstrdup(querystr);
}
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com