| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Brooks Lyrette <brooks(dot)lyrette(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:21:10 |
| Message-ID: | dcc563d10911021421sc8046fal1d75beca5619a10d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | Brooks Lyrette | 2009-11-02 22:56:39 | Re: Help with postgresql memory issue |
| Previous Message | Raimon Fernandez | 2009-11-02 21:57:30 | Re: Cancelling Requests Frontend/Backend Protocol TCP/IP |