Re: Auto-tuning work_mem and maintenance_work_mem

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: Auto-tuning work_mem and maintenance_work_mem
Date: 2013-10-10 02:58:08
Message-ID: 20131010025808.GH7092@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 9, 2013 at 09:34:16PM -0400, Robert Haas wrote:
> On a more pedestrian note, when I try this patch with shared_buffers =
> 8GB, the postmaster won't start. It dies with:
>
> FATAL: -20203 is outside the valid range for parameter "work_mem" (-1
> .. 2147483647)

Fixed with the attached patch:

test=> SHOW shared_buffers;
shared_buffers
----------------
8GB
(1 row)

test=> SHOW work_mem;
work_mem
----------
21739kB
(1 row)

test=> SHOW maintenance_work_mem;
maintenance_work_mem
----------------------
699050kB
(1 row)

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

Attachment Content-Type Size
work_mem.diff text/x-diff 8.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-10-10 03:02:13 Re: Auto-tuning work_mem and maintenance_work_mem
Previous Message Peter Eisentraut 2013-10-10 02:43:20 pgsql: Revive line type