Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199508281308.GAA08673@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
Message-Id: <199508281308.GAA08505@nobozo.CS.Berkeley.EDU>
To: postgres@postgres.Berkeley.EDU
Subject: Memory Leaks
Date: Mon, 28 Aug 1995 14:08:05 +0100
From: Alan Byrne <alan@nova.ucd.ie>
Resent-To: postgres-redist@postgres.Berkeley.EDU
Resent-Date: Mon, 28 Aug 95 06:08:32 -0700
Resent-XMts: smtp


Hello all,

Has anyone out there done anything about tidying up the libpq frontend stuff -
it seems to leak memory like a sieve.

We have been using Postgres as a backend engine to service Web Publishing for
almost a year now but the latest caching version requires us to have a
daemon processing database queries.  At the moment each request will lose
8K or so.

Problem areas seem to be in:

pq_connect() - Connection and Port structures.
pq_global_init() - Environment Variables.

but there may be more ?

Any or all suggestions welcome.

Alan Byrne.
email: alan@nova.ucd.ie

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
              URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/