| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, hlinnaka(at)iki(dot)fi |
| Cc: | 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 19:05:26 |
| Message-ID: | 54F605F6.3080107@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-03-03 19:32:32 | Re: plpgsql versus domains |
| Previous Message | Josh Berkus | 2015-03-03 19:04:30 | Re: Patch: raise default for max_wal_segments to 1GB |