| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "J(dot)T(dot) Hartzler" <dba(at)wap(dot)ntelos(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: kernel memory parms |
| Date: | 2003-03-24 21:48:30 |
| Message-ID: | 20607.1048542510@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"J.T. Hartzler" <dba(at)wap(dot)ntelos(dot)com> writes:
> Based on what I read in the docs I should be able to use at
> setting of shared_buffers = 454000 in my postgresql.conf file as I want
> to use about 3600MB of memory for my database.
This is a bad idea in any case, even if your kernel would let you do it.
Try configuring a couple thousand shared_buffers to start out with.
You can find lots of discussion of this topic in the archives, but the
key point is that kernel disk cache is a perfectly effective use of RAM.
You don't need to, and shouldn't try to, make Postgres buffers occupy
all of RAM, or even a very large percentage of it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michelle Konzack | 2003-03-25 12:03:35 | Re: Cross-Platform development |
| Previous Message | Josh Berkus | 2003-03-24 21:47:19 | Re: kernel memory parms |