Skip site navigation (1) Skip section navigation (2)

Re: maintenance_work_mem and autovacuum

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Josh Berkus <josh(at)agliodbs(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: maintenance_work_mem and autovacuum
Date: 2009-03-26 21:29:16
Message-ID: 86D5C19DB18D86789964F7D9@teje (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
--On Donnerstag, März 26, 2009 13:43:45 -0700 Josh Berkus 
<josh(at)agliodbs(dot)com> wrote:

> I actually have a client who does both automated and manual vacuums.
> Having two settings would definitely be convenient for them.

I often found people doing this running within a) their own superuser with 
special GUCs set or b) using their own scripts which are setting 
maintenance_work_mem accordingly.

Often people are very confused about the number of *_vaccum_* settings 
already present: they sometimes have a really hard time to learn the 
difference between manual and auto vaccum and the interaction of 
default/inherited settings.

That said, having a separate setting would be consequent, but it seems to 
me it's enough there to satisfy all needs, isn't it?



In response to

pgsql-hackers by date

Next:From: Emmanuel CecchetDate: 2009-03-26 22:08:02
Subject: Re: Partitioning feature ...
Previous:From: Josh BerkusDate: 2009-03-26 21:29:06
Subject: Re: maintenance_work_mem and autovacuum

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group