| From: | Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: effective_cache_size on 32-bits postgres |
| Date: | 2013-03-18 18:18:08 |
| Message-ID: | CANs8QJaNdx0Y7jK5a7rEC0kfQCXHGQsTXeuMbu3Ep1xMCTUr0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Ok, now I'm lost, who is right about the limit? Rob or Pavel?
Rob, I know it should be a 64 bit, and it will be soon, but there are good
reasons for this scenario and it's ok for now.
On Mon, Mar 18, 2013 at 3:15 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>wrote:
> 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
>
> Regards
>
> Pavel
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-03-18 18:18:37 | Re: effective_cache_size on 32-bits postgres |
| Previous Message | Pavel Stehule | 2013-03-18 18:15:37 | Re: effective_cache_size on 32-bits postgres |