| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Daulat Ram <Daulat(dot)Ram(at)exponential(dot)com>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Shared_buffers |
| Date: | 2019-03-12 19:23:52 |
| Message-ID: | CAHOFxGqT24bb_G9Ej3jAwBDLizfK1dwb+rXo62mP4zjB6iDRpA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Mar 12, 2019 at 2:29 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> Daulat Ram wrote:
> > I want to know about the working and importance of shared_buffers in
> Postgresql?
> > is it similar to the oracle database buffer cache?
>
> Yes, exactly.
>
> The main difference is that PostgreSQL uses buffered I/O, while Oracle
> usually
> uses direct I/O.
>
> Usually you start with shared_buffers being the minimum of a quarter of the
> available RAM and 8 GB.
>
Any good rule of thumb or write up about when shared buffers in excess of
8GBs makes sense (assuming system ram 64+ GBs perhaps)?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MichaelDBA | 2019-03-12 20:03:11 | Re: Shared_buffers |
| Previous Message | Laurenz Albe | 2019-03-12 08:29:13 | Re: Shared_buffers |