| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fernando Schapachnik <fpscha(at)via-net-works(dot)net(dot)ar> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Neverending query on 6.5.2 over Solaris 2.5.1 |
| Date: | 1999-10-22 15:33:56 |
| Message-ID: | 20677.940606436@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fernando Schapachnik <fpscha(at)ns1(dot)via-net-works(dot)net(dot)ar> writes:
>> enough buffer space to avoid thrashing. You need to increase your
>> kernel's max-shared-memory-block-size (SHMMAX, I think) parameter
>> so that you can run with a more reasonable -B setting. A lot of
>> kernels ship with SHMMAX settings that are ridiculously small for
>> any modern machine.
> What value would you advise for shmmax?
Well, with the default number of buffers (64) Postgres requires about
a megabyte (I think a tad over 1Mb, in 6.5.*). Extra buffers are 8K
plus a little overhead apiece. If you are running with more than a
couple of active backends at a time then you probably want to use
more than the default number of buffers. But I have no advice on
how many is appropriate for what size of installation --- can anyone
else help?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brian E Gallew | 1999-10-22 15:57:11 | Re: [HACKERS] Neverending query on 6.5.2 over Solaris 2.5.1 |
| Previous Message | Jimmie Houchin | 1999-10-22 15:32:27 | Re: [GENERAL] Re: What's WAL |