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

Re: [HACKERS] Vacuum Delay feature

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>,PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Vacuum Delay feature
Date: 2004-02-12 20:22:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Bruce Momjian wrote:

> Jan Wieck wrote:
>> Attached is a corrected version that solves the query cancel problem by 
>> not napping any more and going full speed as soon as any signal is 
>> pending. If nobody objects, I'm going to commit this tomorrow.
> Jan, three questions.  First, is this useful now that we have the new
> cache replacement code, second, do we need this many parameters (can't
> any of them be autotuned), and third, what about documentation?

You mean if stopping to nap is useful when a signal is pending or if 
napping during vacuum itself is useful at all?

I am willing to make it all self tuning and automagic. Just tell me how.

Documentation is missing so far. Will work on that.


# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2004-02-12 20:38:35
Subject: Re: [HACKERS] Vacuum Delay feature
Previous:From: Rich HallDate: 2004-02-12 20:18:51
Subject: Re: Transaction aborts on syntax error.

pgsql-patches by date

Next:From: Magnus HaganderDate: 2004-02-12 20:22:43
Subject: win32 setitimer implementation
Previous:From: Bruce MomjianDate: 2004-02-12 19:58:17
Subject: Re: Patch for psql startup clarity

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