pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tim Brookes <tim.brookes@mcmail.com>
Cc: Lamar Owen <lamar.owen@wgcr.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: libpq++ tracing considered harmful (was Re: libpq++ memory problems)
Date: Tue, 16 May 2000 10:04:40 -0400
Message-ID: <10624.958485880@sss.pgh.pa.us> (raw)
In-Reply-To: <392117E9.D8118E6C@mcmail.com>
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>
	<8280.956254952@sss.pgh.pa.us>
	<38FF4C3F.D79FCF4D@wgcr.org>
	<8424.956255864@sss.pgh.pa.us>
	<392117E9.D8118E6C@mcmail.com>

Tim Brookes <tim.brookes@mcmail.com> writes:
> I have repeated my previous test, and found I am still leaking huge
> amounts of memory.

Hmph.  Are you sure you are releasing query results when you're done
with them?

			regards, tom lane



view thread (6+ messages)  latest in thread

Message-ID: <10624.958485880@sss.pgh.pa.us>
Permalink:  ../10624.958485880@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10624.958485880@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, lamar.owen@wgcr.org
  Subject: Re: libpq++ tracing considered harmful (was Re: libpq++ memory problems)
  In-Reply-To: <10624.958485880@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