Re: Patch: raise default for max_wal_segments to 1GB
От | Corey Huinker |
---|---|
Тема | Re: Patch: raise default for max_wal_segments to 1GB |
Дата | |
Msg-id | CADkLM=fm7GBwvVc=c0t9DExmvVx9joU0XHOEx4wtpcBUjAjYgA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Patch: raise default for max_wal_segments to 1GB (Josh Berkus <josh@agliodbs.com>) |
Список | pgsql-hackers |
<div dir="ltr">No intention to hijack. Dropping issue for now.</div><div class="gmail_extra"><br /><div class="gmail_quote">OnTue, Mar 3, 2015 at 2:05 PM, Josh Berkus <span dir="ltr"><<a href="mailto:josh@agliodbs.com" target="_blank">josh@agliodbs.com</a>></span>wrote:<br /><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px#ccc solid;padding-left:1ex"><span class="">On 03/03/2015 10:58 AM, Corey Huinker wrote:<br /> > Naivequestion: would it be /possible/ to change configuration to accept<br /> > percentages, and have a percent mean "ofexisting RAM at startup time"?<br /> ><br /> > I ask because most of the tuning guidelines I see suggest settingmemory<br /> > parameters as a % of RAM available.<br /><br /></span>Waaaaaaay off topic for this thread. Pleasedon't hijack; start a new<br /> thread if you want to discuss this.<br /><div class="HOEnZb"><div class="h5"><br />--<br /> Josh Berkus<br /> PostgreSQL Experts Inc.<br /><a href="http://pgexperts.com" target="_blank">http://pgexperts.com</a><br/></div></div></blockquote></div><br /></div>
В списке pgsql-hackers по дате отправления: