| From: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
|---|---|
| To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Tuning 8.3 |
| Date: | 2008-02-25 16:27:17 |
| Message-ID: | 1A6E6D554222284AB25ABE3229A9276271564C@nrtexcus702.int.asurion.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I need to run about 1000 PostgreSQL connections on a server that I
can
> > use about 4 GB of the total 16 GB of total RAM. It seems that each
> > session creates a process that uses about 15 MB of RAM just for
> > connecting so I'm running out of RAM rather quickly.
>
> I think you're being bitten by a different problem than it appears.
> Windows
> has a fixed size per-session shared memory pool which runs out rather
> quickly.
> You can raise that parameter though. (The 125 mentioned there is
raised to
> about 300 with Pg 8.3.)
>
> See:
>
> http://www.postgresql.org/docs/faqs.FAQ_windows.html#4.4
>
>
Thanks for the tip and I'll be moving this to the performance forum.
Although, with 8.3, it seems that the FAQ is out of date?
Jon
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-25 16:29:39 | Re: Questions about indexes with text_pattern_ops |
| Previous Message | Gregory Stark | 2008-02-25 16:23:39 | Re: Tuning 8.3 |