| From: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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 20:03:11 |
| Message-ID: | 5C88107F.7040902@sqlexec.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Set shared_buffers more accurately by using pg_buffercache extension and
the related queries during high load times.
Regards,
Michael Vitale
> Michael Lewis <mailto:mlewis(at)entrata(dot)com>
> Tuesday, March 12, 2019 3:23 PM
> On Tue, Mar 12, 2019 at 2:29 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at
> <mailto: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 | Justin Pryzby | 2019-03-12 20:11:02 | Re: Shared_buffers |
| Previous Message | Michael Lewis | 2019-03-12 19:23:52 | Re: Shared_buffers |