Re: libpq++ tracing considered harmfu[Fwd: libpq++ tracing considered harmful (was Re: libpq++ memory problems)]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: root <tim(dot)brookes(at)mcmail(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: libpq++ tracing considered harmfu[Fwd: libpq++ tracing considered harmful (was Re: libpq++ memory problems)]
Date: 2000-05-22 16:19:06
Message-ID: 18279.959012346@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

root <tim(dot)brookes(at)mcmail(dot)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

Browse pgsql-hackers by date

  From Date Subject
Next Message Murad Nayal 2000-05-22 16:42:48 port v7.0 to SGI-IRIX-6.5.7/64
Previous Message Ross J. Reedstrom 2000-05-22 15:58:41 Re: A test to add to the crashme test

Browse pgsql-interfaces by date

  From Date Subject
Next Message Ragnar Hakonarson 2000-05-22 18:54:59 plperl difficulties
Previous Message Jaume 2000-05-22 10:54:50 JDBC date - Timestamp problem