Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Sat, 19 Apr 2008 08:57:11 +0300
- Message-id: <480989B7(dot)3050806(at)enterprisedb(dot)com>
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 ---------------------- 16384That 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
- References:
- 3-days-long vacuum of 20GB table
- From: Jeffrey Baker
- Re: 3-days-long vacuum of 20GB table
- From: Tom Lane
- Re: 3-days-long vacuum of 20GB table
- From: Jeffrey Baker
- Re: 3-days-long vacuum of 20GB table
- From: Jeffrey Baker
- 3-days-long vacuum of 20GB table
- Prev by Date: Re: Message queue table..
- Next by Date: Re: Background writer underemphasized ...
- Previous by thread: Re: 3-days-long vacuum of 20GB table
- Next by thread: Message queue table..
- Indexes: