From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Indika Maligaspe" <indika(at)rezgateway(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Postgress memory leak with JBoss3.2.6 and large DB |
Date: | 2006-08-31 18:11:03 |
Message-ID: | 7F1AB951-EF24-427A-A282-22684E520CA1@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 31-Aug-06, at 1:54 PM, Tom Lane wrote:
> "Indika Maligaspe" <indika(at)rezgateway(dot)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(at)postgresql(dot)org so that
> your
> message can get through to the mailing list cleanly
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2006-08-31 18:13:40 | Re: High concurrency OLTP database performance tuning |
Previous Message | Vivek Khera | 2006-08-31 18:10:55 | Re: performance problems. |