Postgres Pro
Downloads
Home   >   mailing lists

Re: Memory leak in FDW - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Memory leak in FDW
Date
Msg-id 10762.1303842642@sss.pgh.pa.us
Whole thread Raw
In response to Memory leak in FDW  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Memory leak in FDW  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Tree view 
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> The trivial fix is to reset the per-tuple memory context between 
> iterations.

Have you tested this with SRFs?

ForeignNext seems like quite the wrong place for resetting
exprcontext in any case ...
        regards, tom lane

pgsql-hackers by date:

Previous
From: Christopher Browne
Date:
Subject: Re: Proposal - asynchronous functions
Next
From: Dann Corbit
Date:
Subject: What was the exact version of PostgreSQL where the column name length changed from 31 to 63 characters?