| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tom Allison <tallison(at)tacocat(dot)net> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: memory |
| Date: | 2006-11-10 01:58:59 |
| Message-ID: | 14565.1163123939@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Tom Allison <tallison(at)tacocat(dot)net> writes:
> I've a relatively small machine (512MB) that I am setting up as a small area
> database server. And I was trying to get the memory balanced out for this
> machine. I don't plan on running anything other than postgresql and whatever
> might be required to operate sanely on the network.
> So I was changing my shared buffers and found I couldn't really get over 3500
> before SHMMAX started complaining.
Well, that's only about 28MB. A lot of systems have unreasonably small
SHMMAX settings (historical leftover); you might try increasing yours.
If you're running something older than PG 8.1, it's not necessarily
worth your trouble to increase shared_buffers beyond that, but in 8.1
I'd encourage you to try going higher.
> So, I'm trying to understand why I don't have more memory being used
> up by these SQL jobs. I was assuming that running 100 SQL
> statements/second would suck up a lot of memory.
Not necessarily. How much data do they touch?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-11-10 02:05:14 | Re: memory |
| Previous Message | Tom Allison | 2006-11-10 01:50:24 | memory |