From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dawn Hollingsworth <dmh@airdefense.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres Connections Requiring Large Amounts of Memory
Date: Mon, 16 Jun 2003 16:45:02 -0400
Message-ID: <6634.1055796302@sss.pgh.pa.us> (raw)
In-Reply-To: <1055752337.2182.49.camel@kaos>
References: <1055752337.2182.49.camel@kaos>
Dawn Hollingsworth <dmh@airdefense.net> writes:
> PostgreSQL Version: 7.2.3
> My problem is that the memory used by the connections appears to grow
> over time, especially when the amount of data entering the system is
> increased.
We have fixed memory-leak problems in the past, and I wouldn't be
surprised if some remain, but you'll have to give a lot more detail
about what you're doing if you want help. A leak that persists across
transaction boundaries is fairly surprising --- I think I can safely
say that there are none in the normal code paths. I'm guessing you must
be using some off-the-beaten-path feature.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, dmh@airdefense.net
Subject: Re: Postgres Connections Requiring Large Amounts of Memory
In-Reply-To: <6634.1055796302@sss.pgh.pa.us>
References: <1055752337.2182.49.camel@kaos> <6634.1055796302@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