| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Kevin Grittner <kgrittn(at)ymail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Auto-tuning work_mem and maintenance_work_mem |
| Date: | 2013-10-10 18:44:51 |
| Message-ID: | CAM3SWZSW7XtxJVU=FgkWzgjBfS1uMKoVcPT-hp4oi7J=FbYrmw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 10, 2013 at 11:43 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Oct 10, 2013 at 1:37 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> So, the question is: can we reasonably determine, at initdb time, how
>> much RAM the system has?
>
> As long as you are willing to write platform-dependent code, yes.
That's why trying to give the responsibility to a packager is compelling.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-10-10 18:45:18 | Re: dynamic shared memory: wherein I am punished for good intentions |
| Previous Message | Peter Eisentraut | 2013-10-10 18:44:12 | Re: Auto-tuning work_mem and maintenance_work_mem |