From: Jeff Davis <pgsql@j-davis.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: The shared buffers challenge
Date: Fri, 27 May 2011 17:19:01 -0700
Message-ID: <1306541941.32559.119.camel@jdavis-ux.asterdata.local> (raw)
In-Reply-To: <BANLkTimPC-K_o8XNn1hK4ZgBrTGO_Z6RDw@mail.gmail.com>
References: <BANLkTimPC-K_o8XNn1hK4ZgBrTGO_Z6RDw@mail.gmail.com>
On Thu, 2011-05-26 at 09:31 -0500, Merlin Moncure wrote:
> Where they are most helpful is for masking of i/o if
> a page gets dirtied >1 times before it's written out to the heap
Another possible benefit of higher shared_buffers is that it may reduce
WAL flushes. A page cannot be evicted from shared_buffers until the WAL
has been flushed up to the page's LSN ("WAL before data"); so if there
is memory pressure to evict dirty buffers, it may cause extra WAL
flushes.
I'm not sure what the practical effects of this are, however, but it
might be an interesting thing to test.
Regards,
Jeff Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pgsql@j-davis.com, mmoncure@gmail.com
Subject: Re: The shared buffers challenge
In-Reply-To: <1306541941.32559.119.camel@jdavis-ux.asterdata.local>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox