Re: 3-days-long vacuum of 20GB table

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Jeffrey Baker <jwbaker(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org
Subject: Re: 3-days-long vacuum of 20GB table
Date: 2008-04-19 05:57:11
Message-ID: 480989B7.3050806@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jeffrey Baker wrote:
> On Fri, Apr 18, 2008 at 10:32 AM, Jeffrey Baker <jwbaker(at)gmail(dot)com> wrote:
>> # show maintenance_work_mem ;
>> maintenance_work_mem
>> ----------------------
>> 16384
>
> That appears to be the default. I will try increasing this. Can I
> increase it globally from a single backend, so that all other backends
> pick up the change, or do I have to restart the instance?

You can change it in the config file, and send postmaster the HUP
signal, which tells all backends to reload the file. "killall -HUP
postmaster" or similar.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Smith 2008-04-19 09:22:46 Re: Background writer underemphasized ...
Previous Message Chris Browne 2008-04-18 19:57:10 Re: Message queue table..