From: Tom Lane <tgl@sss.pgh.pa.us>
To: jody brownell <jody.brownell@q1labs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres consuming way too much memory???
Date: Thu, 15 Jun 2006 11:34:39 -0400
Message-ID: <28321.1150385679@sss.pgh.pa.us> (raw)
In-Reply-To: <200606151202.50939.jody.brownell@q1labs.com>
References: <200606141618.37849.jody.brownell@q1labs.com>
<200606150901.19201.jody.brownell@q1labs.com>
<200606150915.10306.jody.brownell@q1labs.com>
<200606151202.50939.jody.brownell@q1labs.com>
"jody brownell" <jody.brownell@q1labs.com> writes:
> When postgresql starts to go into this bloating state, I can only make it happen from my java app.
That's interesting. The JDBC driver uses protocol features that aren't
used by psql, so it's possible that the leak is triggered by one of
those features. I wouldn't worry too much about duplicating the problem
from psql anyway --- a Java test case will do fine.
> I am going to try closing the connection after each TX to see if this
> resolves it for now. If not, I will write a java app, stored procedure
> (table etc) reproduce it without our application.
Even if that works around it for you, please pursue getting a test case
together so we can find and fix the underlying problem.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, jody.brownell@q1labs.com
Subject: Re: Postgres consuming way too much memory???
In-Reply-To: <28321.1150385679@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