Re: Patch: raise default for max_wal_segments to 1GB - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: Patch: raise default for max_wal_segments to 1GB
Date
Msg-id CADkLM=fm7GBwvVc=c0t9DExmvVx9joU0XHOEx4wtpcBUjAjYgA@mail.gmail.com
Whole thread
In response to Re: Patch: raise default for max_wal_segments to 1GB  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
No intention to hijack. Dropping issue for now.

On Tue, Mar 3, 2015 at 2:05 PM, Josh Berkus <josh@agliodbs.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

pgsql-hackers by date:

Previous
From: Gavin Flower
Date:
Subject: Re: Patch: raise default for max_wal_segments to 1GB
Next
From: Eric Grinstein
Date:
Subject: Re: Idea: GSoC - Query Rewrite with Materialized Views