mallah.raj...@gmail.com (Rajesh Kumar Mallah) writes:
why is it not a good idea to give end users control over when they
want to run it ?
It's not a particularly good idea to give end users things that they
are likely then to *immediately* use to shoot themselves in the foot.
Turning off
Its nice to know the evolution of autovacuum and i understand that
the suggestion/requirement of autovacuum at lean hours only
was defeating the whole idea.
regds
--rajesh kumar mallah.
On Fri, Feb 13, 2009 at 11:07 PM, Chris Browne cbbro...@acm.org wrote:
mallah.raj...@gmail.com (Rajesh
Rajesh Kumar Mallah mallah.rajesh 'at' gmail.com writes:
our usage pattern is such that peak activity (indicated by load average)
during day time is 10 times during night hours. Autovacuum just puts
more pressure to the system. If less stressing version is used then
Yet it may allow a more
From: Rajesh Kumar Mallah mallah.raj...@gmail.com
Is it possible to configure autovacuum to run only
during certain hours ? We are forced to keep
it off because it pops up during the peak
query hours.
AFAIK not directly within the conf.
However you could probably set up a shell script to
Rajesh Kumar Mallah mallah.rajesh 'at' gmail.com writes:
Hi,
Is it possible to configure autovacuum to run only
during certain hours ? We are forced to keep
it off because it pops up during the peak
query hours.
You'd rather configure the delaying process to not alter too much
performance.
On Wed, Feb 11, 2009 at 7:11 PM, Guillaume Cottenceau g...@mnc.ch wrote:
Rajesh Kumar Mallah mallah.rajesh 'at' gmail.com writes:
Hi,
Is it possible to configure autovacuum to run only
during certain hours ? We are forced to keep
it off because it pops up during the peak
query hours.
Rajesh Kumar Mallah escribió:
why is it not a good idea to give end users control over when they
want to run it ?
It has never been said that we don't want to give the users control.
It's a matter of writing the code. If you want to propose a patch to
add the feature, feel free.
--
Sent via
On Wed, Feb 11, 2009 at 2:57 PM, Rajesh Kumar Mallah
mallah.raj...@gmail.com wrote:
vacuum_cost_delay = 150
vacuum_cost_page_hit = 1
vacuum_cost_page_miss = 10
vacuum_cost_page_dirty = 20
vacuum_cost_limit = 1000
autovacuum_vacuum_cost_delay = 300
why is it not a good idea to give end
On Feb 11, 2009, at 6:57 AM, Rajesh Kumar Mallah wrote:
why is it not a good idea to give end users control over when they
want to run it ?
There's nothing stopping you from just turning off autovacuum and
running vacuum manually. The point of autovacuum is to vacuum as
needed.
--
Sent
[pgsql-performance-ow...@postgresql.org] On Behalf Of Ben
[be...@silentmedia.com]
Sent: Wednesday, February 11, 2009 8:46 AM
To: Rajesh Kumar Mallah
Cc: PostgreSQL Performance
Subject: Re: [PERFORM] scheduling autovacuum at lean hours only.
On Feb 11, 2009, at 6:57 AM, Rajesh Kumar Mallah wrote:
why
On Wed, Feb 11, 2009 at 10:03 PM, Grzegorz Jaśkiewicz gryz...@gmail.com wrote:
On Wed, Feb 11, 2009 at 2:57 PM, Rajesh Kumar Mallah
mallah.raj...@gmail.com wrote:
vacuum_cost_delay = 150
vacuum_cost_page_hit = 1
vacuum_cost_page_miss = 10
vacuum_cost_page_dirty = 20
vacuum_cost_limit =
On Wed, 11 Feb 2009, Scott Carey wrote:
On a large partitioned database, ordinary vacuum is a very very difficult
option.
Most of the time on such a system, most tables are dormant with respect to
writes and never need to be vacuumed. A 'daily vacuum' is likely to take a
full day to run on
On Wed, 2009-02-11 at 22:57 +0530, Rajesh Kumar Mallah wrote:
On Wed, Feb 11, 2009 at 10:03 PM, Grzegorz Jaśkiewicz gryz...@gmail.com
wrote:
On Wed, Feb 11, 2009 at 2:57 PM, Rajesh Kumar Mallah
mallah.raj...@gmail.com wrote:
vacuum_cost_delay = 150
vacuum_cost_page_hit = 1
On Wed, Feb 11, 2009 at 11:30 PM, Brad Nicholson
bnich...@ca.afilias.info wrote:
On Wed, 2009-02-11 at 22:57 +0530, Rajesh Kumar Mallah wrote:
On Wed, Feb 11, 2009 at 10:03 PM, Grzegorz Jaśkiewicz gryz...@gmail.com
wrote:
On Wed, Feb 11, 2009 at 2:57 PM, Rajesh Kumar Mallah
14 matches
Mail list logo
