Re: Patch: raise default for max_wal_segments to 1GB

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: hlinnaka(at)iki(dot)fi, Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Venkata Balaji N <nag1010(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Patch: raise default for max_wal_segments to 1GB
Date: 2015-03-03 20:22:52
Message-ID: CADkLM=fm7GBwvVc=c0t9DExmvVx9joU0XHOEx4wtpcBUjAjYgA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

No intention to hijack. Dropping issue for now.

On Tue, Mar 3, 2015 at 2:05 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:

> On 03/03/2015 10:58 AM, Corey Huinker wrote:
> > Naive question: would it be /possible/ to change configuration to accept
> > percentages, and have a percent mean "of existing RAM at startup time"?
> >
> > I ask because most of the tuning guidelines I see suggest setting memory
> > parameters as a % of RAM available.
>
> Waaaaaaay off topic for this thread. Please don't hijack; start a new
> thread if you want to discuss this.
>
> --
> Josh Berkus
> PostgreSQL Experts Inc.
> http://pgexperts.com
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Eric Grinstein 2015-03-03 20:30:44 Re: Idea: GSoC - Query Rewrite with Materialized Views
Previous Message Gavin Flower 2015-03-03 20:10:34 Re: Patch: raise default for max_wal_segments to 1GB