Re: Vacuum analyse after a long time without one ...
От | Anj Adu |
---|---|
Тема | Re: Vacuum analyse after a long time without one ... |
Дата | |
Msg-id | f2fd819a0909111113q2995dfc7m63ecd71e583b8dd4@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Vacuum analyse after a long time without one ... (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Vacuum analyse after a long time without one ...
|
Список | pgsql-admin |
For a 64 bit machine..does the higher shared buffer setting really offer a significant improvement over a 32 bit lower setting coupled with linux caching ? Is the postgres shared buffer algorithm superior to the linux caching algorithm to favor a switch to 64 bit On Fri, Sep 11, 2009 at 9:50 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Nicolas Michel <nicolas.michel@lemail.be> writes: >> - I have 16Go of RAM on that server (but 32bits OS with bigmem kernel ; >> so I set shared buffer to 350000 (~2,7GB) for a shmmax of 4000000000 >> (~3,8GB) > > On a 32-bit machine that's just insane. You've got something like 300MB > left over in the process address space (assuming the typical 1Gb for > kernel split). No wonder things are falling over. Try putting > shared_buffers somewhere around 1Gb. Or switch to 64-bit. > > regards, tom lane > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin >
В списке pgsql-admin по дате отправления: