Sam Jas wrote:
...
BTW we are using postgreSQL 8.3.2.
red flag. 8.3 is up to 8.3.8, lots of updates since 8.3.2
I attach the release notes for these incremental revisions. note there
are gobs of fixes in many of these releases.you can upgrade 8.3.2
directly to 8.3.8, with only the c
Sam Jas wrote:
> We are running on 64 - bit.
> Whenever the reserved memory in top command it crosses 3.9g it hangs.
> If we try to kill process (using pg_cancel_backend()) it won't kill. At last
> either
> we have to kill all process at OS level or we have to reboot the server.
> After reboot
On Thu, Nov 12, 2009 at 12:10 AM, Sam Jas wrote:
>
> Hi,
>
> We are facing issue with the RES memory. Below is the o/p of top command. It
> shows that writer process reserved 3.8g. We have observed that if it
> increased to 3.9g we need to restart the db. Otherwise it hangs. Kindly
> suggest u
(Please refrain from html email on the list)
On Thu, Nov 12, 2009 at 12:10 AM, Sam Jas wrote:
>
> Hi,
>
> We are facing issue with the RES memory. Below is the o/p of top command. It
> shows that writer process reserved 3.8g. We have observed that if it
> increased to 3.9g we need to restart th
uxton
Subject: Re: [GENERAL] DB Restart
To: "Sam Jas"
Cc: "general"
Date: Thursday, 12 November, 2009, 12:56 PM
Sam Jas wrote:
> Thanks for your reply.
>
> No we are not running OOM. ulimit o/p is as below.
>
> [postg...@server1 ~]$ ulimit
> unlimited
Un
Sam Jas wrote:
> Thanks for your reply.
>
> No we are not running OOM. ulimit o/p is as below.
>
> [postg...@server1 ~]$ ulimit
> unlimited
Unless you are running on a 32-bit system you should be alright then.
What precisely is the problem? What do you mean by the DB "hangs"?
--
Richard H
Thanks for your reply.
No we are not running OOM. ulimit o/p is as below.
[postg...@server1 ~]$ ulimit
unlimited
--- On Thu, 12/11/09, Richard Huxton wrote:
From: Richard Huxton
Subject: Re: [GENERAL] DB Restart
To: "Sam Jas"
Cc: "general"
Date: Thursday, 12 Nove
Sam Jas wrote:
>
>
>
> Hi,
>
> We are facing issue with the RES memory. Below is the o/p of
> top command. It shows that writer process reserved 3.8g. We have observed that
> if it increased to 3.9g we need to restart the db. Otherwise it hangs.
> Kindly suggest us the good way to figure it o
