A follow-up on this:
Should documentation also mention that it does not make sense to set
effective_cache_size < shared_buffers? And maybe it is worth prohibiting
this or at least having a WARNING in logs?
Why: I see setups where with growing RAM and shared_buffers set to
On Mon, Nov 5, 2018 at 02:01:12PM -0300, Alvaro Herrera wrote:
> On 2018-Nov-05, Bruce Momjian wrote:
>
> > Well, here are the lines in guc.c:
> >
> > gettext_noop("Sets the planner's assumption about the size of
> > the data cache."),
> > gettext_noop("That is, the size
On 2018-Nov-05, Bruce Momjian wrote:
> Well, here are the lines in guc.c:
>
> gettext_noop("Sets the planner's assumption about the size of the
> data cache."),
> gettext_noop("That is, the size of the cache used for PostgreSQL
> data files. "
>
On Mon, Nov 5, 2018 at 03:23:03PM +0300, Nikolay Samokhvalov wrote:
>
>
> On Mon, Nov 5, 2018 at 3:01 PM Bruce Momjian wrote:
>
> > > {"effective_cache_size", PGC_USERSET, QUERY_TUNING_COST,
> > > - gettext_n
On Mon, Nov 5, 2018 at 3:01 PM Bruce Momjian wrote:
> > > {"effective_cache_size", PGC_USERSET, QUERY_TUNING_COST,
> > > - gettext_noop("Sets the planner's assumption about
> the size of the disk cache."),
> > >
rc/backend/utils/misc/guc.c
> > @@ -2987,10 +2987,9 @@ static struct config_int ConfigureNamesInt[] =
> >
> > {
> > {"effective_cache_size", PGC_USERSET, QUERY_TUNING_COST,
> > - gettext_noop(&
nfigureNamesInt[] =
>
> {
> {"effective_cache_size", PGC_USERSET, QUERY_TUNING_COST,
> - gettext_noop("Sets the planner's assumption about the
> size of the disk cache."),
> - gettext_noo
variable descriptions.
> > Second, unify the description of effective_cache_size to talk about
> > storage cache size, not just kernel storage cache, and maybe even talk
> > about the double buffering effect.
>
> I have attached a patch for the second item, which I would
On Thu, Oct 11, 2018 at 01:48:49PM -0400, Bruce Momjian wrote:
> So, I think there are two action items here. First, rename "disk" to
> "drive" or "storage" in the docs and server variable descriptions.
> Second, unify the description of effective_cache_
On Thu, Sep 13, 2018 at 03:14:08PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.6/static/runtime-config-query.html
> Description:
>
> Hi,
>
> The effective_cache_siz
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/runtime-config-query.html
Description:
Hi,
The effective_cache_size documentation (section 19.7) is: "When setting this
parameter you should consider both PostgreSQL
11 matches
Mail list logo
