Skip site navigation (1) Skip section navigation (2)

Re: Memory leak in FDW

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Memory leak in FDW
Date: 2011-04-26 18:30:42
Message-ID: 10762.1303842642@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Dann CorbitDate: 2011-04-26 18:35:57
Subject: What was the exact version of PostgreSQL where the column name length changed from 31 to 63 characters?
Previous:From: Christopher BrowneDate: 2011-04-26 18:30:23
Subject: Re: Proposal - asynchronous functions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group