public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jan Wieck <[email protected]>
To: Tom Lane <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Justin Clift <[email protected]>
Cc: [email protected]
Subject: Re: [pgsql-www] pg_autovacuum is nice ... but ...
Date: Mon, 08 Nov 2004 11:40:25 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 11/4/2004 5:44 PM, Tom Lane wrote:

> "Marc G. Fournier" <[email protected]> writes:
>> Moved to -hackers where this belongs :)
> 
>> On Fri, 5 Nov 2004, Justin Clift wrote:
>>> Would making max_fsm_relations and max_fsm_pages dynamically update 
>>> themselves whilst PostgreSQL runs be useful?
> 
> Possibly, but it isn't happening in the foreseeable future, for the same
> reason that we don't auto-update shared_buffers and the other shared
> memory sizing parameters: we can't resize shared memory on the fly.
> 
>> I'm not sure if I like this one too much ... but it would be nice if 
>> something like this triggered a warning in the logs, maybe a feature of 
>> pg_autovacuum itself?
> 
> autovacuum would probably be a reasonable place to put it.  We don't
> currently have any good way for autovacuum to get at the information,
> but I suppose that an integrated autovacuum daemon could do so.

Don't know why this must be an "integrated" autovacuum. Can't the info 
about the FSM usage be presented as system views?


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== [email protected] #

view thread (24+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [pgsql-www] pg_autovacuum is nice ... but ...
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox