Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id MAA07480;
	Mon, 22 May 2000 12:19:09 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id MAA18282;
	Mon, 22 May 2000 12:19:07 -0400 (EDT)
To: root <tim.brookes@mcmail.com>
cc: pgsql-interfaces@postgresql.org, pgsql-hackers@postgresql.org
Subject: Re: libpq++ tracing considered harmfu[Fwd: libpq++ tracing considered
	harmful (was Re: libpq++ memory problems)]
In-reply-to: <3928F2F4.C69AFB45@mcmail.com> 
References: <3928F2F4.C69AFB45@mcmail.com>
Comments: In-reply-to root <tim.brookes@mcmail.com>
	message dated "Mon, 22 May 2000 09:42:28 +0100"
Date: Mon, 22 May 2000 12:19:06 -0400
Message-ID: <18279.959012346@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200005/31

root <tim.brookes@mcmail.com> writes:
> What do I need to change to stop the leak on the postmaster?

Get rid of the getprotobyname call (essentially the same change
as in fe-connect.c) in src/backend/libpq/pqcomm.c.

You could just grab last night's snapshot tarball; it should
have those fixes in it already.

			regards, tom lane