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 OAA46323 for ; Thu, 20 Apr 2000 14:22:59 -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 OAA08283; Thu, 20 Apr 2000 14:22:33 -0400 (EDT) To: Lamar Owen cc: Tim Brookes , pgsql-interfaces@postgresql.org Subject: Re: libpq++ tracing considered harmful (was Re: libpq++ memory problems) In-reply-to: <38FF471B.4463ECF2@wgcr.org> References: <38FB6FA1.C63B030B@mcmail.com> <16483.956019092@sss.pgh.pa.us> <38FEB8DB.DBC3460E@mcmail.com> <2182.956243193@sss.pgh.pa.us> <38FF2126.9525DB82@mcmail.com> <38FF243E.E5C0E87E@wgcr.org> <8163.956252492@sss.pgh.pa.us> <38FF471B.4463ECF2@wgcr.org> Comments: In-reply-to Lamar Owen message dated "Thu, 20 Apr 2000 14:06:19 -0400" Date: Thu, 20 Apr 2000 14:22:32 -0400 Message-ID: <8280.956254952@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200004/170 Lamar Owen writes: >> Perhaps something can be salvaged from the wreckage, but for now the >> right answer is just to make sure that this code is not compiled. > And to compile this code you supply _which_ configure option? It isn't a configure option --- you have to edit libpq++'s makefile to enable it. Or, in the case of the 6.5.* code, it got turned on anyway :-(. Fortunately there is no security hole in either 6.5.* or current, since the code is too broken to actually produce any trace output, compiled or not. My point was mainly that I thought we should remove the code rather than fix it. regards, tom lane