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

Re: Memory leak in FDW

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
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:15:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Excerpts from Heikki Linnakangas's message of mar abr 26 15:06:51 -0300 2011:

> I tried to look around for other executor nodes that might 
> have the same problem. I didn't see any obvious leaks, although index 
> scan node seems to call AM's getnext without resetting the memory 
> context in between. That's a pretty well-tested codepath, however, and 
> there hasn't been any complains of leaks with index scans, so there must 
> be something that mitigates it.

Don't we have some rule that functions used in index AMs are supposed to
be leak-free?

Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to


pgsql-hackers by date

Next:From: Christopher BrowneDate: 2011-04-26 18:30:23
Subject: Re: Proposal - asynchronous functions
Previous:From: Heikki LinnakangasDate: 2011-04-26 18:06:51
Subject: Memory leak in FDW

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