pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: root <tim.brookes@mcmail.com>
Cc: pgsql-interfaces@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: libpq++ tracing considered harmfu[Fwd: libpq++ tracing considered harmful (was Re: libpq++ memory problems)]
Date: Mon, 22 May 2000 12:19:06 -0400
Message-ID: <18279.959012346@sss.pgh.pa.us> (raw)
In-Reply-To: <3928F2F4.C69AFB45@mcmail.com>
References: <3928F2F4.C69AFB45@mcmail.com>

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



Message-ID: <18279.959012346@sss.pgh.pa.us>
Permalink:  ../18279.959012346@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/18279.959012346@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: tgl@sss.pgh.pa.us, tim.brookes@mcmail.com, pgsql-hackers@postgresql.org
  Subject: Re: libpq++ tracing considered harmfu[Fwd: libpq++ tracing considered harmful (was Re: libpq++ memory problems)]
  In-Reply-To: <18279.959012346@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox