From: | Brooks Lyrette <brooks(dot)lyrette(at)gmail(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Help with postgresql memory issue |
Date: | 2009-11-02 22:56:39 |
Message-ID: | B9F93F42-48C3-404C-8FEC-116E3BFA25F4@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I wish the solution was that simple. I rent the zone and that is my
providers cap.
On 2-Nov-09, at 5:21 PM, Scott Marlowe wrote:
> On Mon, Nov 2, 2009 at 1:11 PM, Brooks Lyrette <brooks(dot)lyrette(at)gmail(dot)com
> > wrote:
>> Thanks for all the help guys.
>> So this is what I get from all this. My solaris zone will cap me at
>> around
>> 900M-1000M RSS memory. Therefore using the math from a pervious
>> reply I can
>> only have about 23 connections to my database without maxing out the
>> machines memory?
>> This seems a little low, won't postgres start swapping to disk once
>> the
>> available RAM is used up?
>
> pgsql doesn't swap, the OS swaps, when it runs out of memory. Since
> pgsql is limited to 1G, the OS has no reason to swap.
>
> Can you simply remove the cap from this instance? It doesn't seem to
> be doing anything useful.
From | Date | Subject | |
---|---|---|---|
Next Message | Viktor Rosenfeld | 2009-11-02 23:25:04 | R-Trees in PostgreSQL |
Previous Message | Scott Marlowe | 2009-11-02 22:21:10 | Re: Help with postgresql memory issue |