| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
| Cc: | Michael Lewis <mlewis(at)entrata(dot)com>, 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:11:02 |
| Message-ID: | 20190312201102.GI23597@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Mar 12, 2019 at 04:03:11PM -0400, MichaelDBA wrote:
> Set shared_buffers more accurately by using pg_buffercache extension and the
> related queries during high load times.
I've tuned ~40 postgres instances, primarily using log_checkpoints and
pg_stat_bgwriter, with custom RRD graphs. pg_buffercache does provide some
valuable insights, and I know it's commonly suggested to check histogram of
usagecounts, but I've never had any idea how to apply that to tune
shared_buffers.
Could you elaborate on what procedure you suggest ?
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MichaelDBA | 2019-03-12 20:11:49 | Re: Shared_buffers |
| Previous Message | MichaelDBA | 2019-03-12 20:03:11 | Re: Shared_buffers |