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

Re: Memory leak

From: "Spencer Quin" <squin(at)rim(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>, "Thomas Parry" <TParry(at)rim(dot)com>,"Geoffrey Stitt" <gstitt(at)rim(dot)com>
Subject: Re: Memory leak
Date: 2004-08-24 20:24:14
Message-ID: 7F0B5938B08C9345BA58ED090AA813F402BCEA04@XCL02YKF.rim.net (view raw or flat)
Thread:
Lists: pgsql-bugs
That's a good theory.  I will definitely check it out.
I appreciate you looking into this Tom.
	Spence

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us] 
Sent: Tuesday, August 24, 2004 4:13 PM
To: Spencer Quin
Cc: pgsql-bugs(at)postgresql(dot)org; Thomas Parry; Geoffrey Stitt
Subject: Re: [BUGS] Memory leak 

"Spencer Quin" <squin(at)rim(dot)com> writes:
> I have found a memory leak in the libpq library for postrgesql 7.4.3.
> The code sample in the attached file will produce the error.

The traceback says that the leak is in libresolv, not libpq.  I'm not
sure it's really a leak at all --- I'd expect libresolv to do some
internal caching, and this looks like it could be data that's just being
held onto for possible reuse.  But in any case you want to file this
report with somebody else.

			regards, tom lane


pgsql-bugs by date

Next:From: PostgreSQL Bugs ListDate: 2004-08-24 20:52:29
Subject: BUG #1230: mirror problem
Previous:From: Tom LaneDate: 2004-08-24 20:12:49
Subject: Re: Memory leak

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