| From: | Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: effective_cache_size on 32-bits postgres |
| Date: | 2013-03-18 18:23:56 |
| Message-ID: | CANs8QJYt3C6TptfzEbCMSJvEwHh1prrtFhpNgXyc9P0z5ApANw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
So setting this as half of ram, as suggested in postgres tuning webpage
should be safe?
It says it is a conservative value...
On Mon, Mar 18, 2013 at 3:18 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>wrote:
> 2013/3/18 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> > Hello
> >
> > 2013/3/18 Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com>:
> >> Hi guys, I am worried about the effective_cache_size.
> >> I run a 32-bits postgres installation on a machine with 64 bits kernel.
> >> Should I limit effective_cache_size to a maximum of 2.5gb?
> >
> > sure and probably little bit less
>
> wrong reply - Rob has true
>
> Pavel
>
> >
> > Regards
> >
> > Pavel
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-03-18 18:33:49 | Re: effective_cache_size on 32-bits postgres |
| Previous Message | Pavel Stehule | 2013-03-18 18:18:37 | Re: effective_cache_size on 32-bits postgres |