| From: | Saurabh Dave <saurabhdave(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Queries very slow and memory consumption too high |
| Date: | 2009-06-23 08:44:03 |
| Message-ID: | fdd0c0f90906230144n26e77f5cgf8e282631e46d72@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
>>If your problem is something that develops over time, one thing
>>you could watch out for are resource leaks, most prominently
>>memory leaks.
What is the recommended way to do that? It seems postgres uses shared
memory, and we have 15 connections all taking up around 35MB as per task
manager OR top. We are not able to figure out definitatively if there is a
memory leak.
Help/Clues??? Thanks all for your responses so far.
- Saurabh
On Tue, Jun 23, 2009 at 1:35 PM, Craig Ringer
<craig(at)postnewspapers(dot)com(dot)au>wrote:
> On Tue, 2009-06-23 at 09:38 +0200, Albe Laurenz wrote:
>
> > Moving to 8.3.7 (what is 8.3.7.1?), on the other hand, is certainly
> > a good thing.
>
> Probably a Linux distro packaging thing, or a Windows installer
> revision. On my Ubuntu 9.04 box for example, `dpkg -l postgresql-8.3'
> reports Pg's version as 8.3.7-1 . The -1 is the Debian package revision,
> but people may not know that.
>
> --
> Craig Ringer
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2009-06-23 09:51:15 | Re: Queries very slow and memory consumption too high |
| Previous Message | Craig Ringer | 2009-06-23 08:05:19 | Re: Queries very slow and memory consumption too high |