pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Cramer <pg@fastcrypt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Indika Maligaspe <indika@rezgateway.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgress memory leak with JBoss3.2.6 and large DB
Date: Thu, 31 Aug 2006 14:11:03 -0400
Message-ID: <7F1AB951-EF24-427A-A282-22684E520CA1@fastcrypt.com> (raw)
In-Reply-To: <21864.1157046887@sss.pgh.pa.us>
References: <20060831095135.4292E9D7@dm17.mta.everyone.net>
	<21864.1157046887@sss.pgh.pa.us>


On 31-Aug-06, at 1:54 PM, Tom Lane wrote:

> "Indika Maligaspe" <indika@rezgateway.com> writes:
>> The problem is when we are querying a specific set of table (which  
>> all
>> tables having over 100K  of rows), the Postgres user process takes  
>> over or
>> close 700MB of memory. This is just to return 3000 odd rows. Even  
>> though we
>> have lot of data we still do not have that much to eat up this  
>> much of
>> memory.
>
> Playing with server-side settings won't have the slightest effect on a
> client-side problem.  I'd suggest asking about this on the pgsql-jdbc
> list; they are more likely to have useful suggestions than backend
> hackers will.

What is the query here. I doubt this is a client side problem, as we  
are still looking at the server side processes, not the java  
processes here.

Also your memory settings are *way* too low
Dave
>
> 			regards, tom lane
>
> ---------------------------(end of  
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that  
> your
>        message can get through to the mailing list cleanly
>




view thread (5+ messages)  latest in thread

Message-ID: <7F1AB951-EF24-427A-A282-22684E520CA1@fastcrypt.com>
Permalink:  ../7F1AB951-EF24-427A-A282-22684E520CA1@fastcrypt.com/
Also on:    postgresql.org/message-id/7F1AB951-EF24-427A-A282-22684E520CA1@fastcrypt.com

 · 

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 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: pg@fastcrypt.com, tgl@sss.pgh.pa.us, indika@rezgateway.com
  Subject: Re: Postgress memory leak with JBoss3.2.6 and large DB
  In-Reply-To: <7F1AB951-EF24-427A-A282-22684E520CA1@fastcrypt.com>
  References: <20060831095135.4292E9D7@dm17.mta.everyone.net> <21864.1157046887@sss.pgh.pa.us> <7F1AB951-EF24-427A-A282-22684E520CA1@fastcrypt.com>

* 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