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

Re: [PATCHES] A way to let Vacuum warn if FSM settings are low. [final?]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>,Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-general(at)postgresql(dot)org,pgsql-patches(at)postgresql(dot)org
Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low. [final?]
Date: 2005-03-14 06:40:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Ron Mayer wrote:
>> My reasoning why I thought the log file was more useful was
>> that only an admin with access to the log files could really
>> do anything about the message anyway.

> The log file is useful, but I think showing the VACUUM user is _more_
> useful than the log file.

I think that reasoning is fundamentally unsound, because (a) a lot of
people already do vacuuming via a cron job or autovacuum, and (b)
autovacuum is definitely the wave of the future.  So it's foolish
to design this messaging around the assumption that there will be
a human attentive to the on-line output from VACUUM.  We should be
ensuring that the message gets into the postmaster log --- whether
it gets sent to the client is secondary.

			regards, tom lane

In response to


pgsql-patches by date

Next:From: David FetterDate: 2005-03-14 06:42:07
Subject: [ Clean up SGML for openjade]
Previous:From: David FetterDate: 2005-03-14 06:23:19
Subject: Clean up SGML for openjade

pgsql-general by date

Next:From: Simon RiggsDate: 2005-03-14 08:17:48
Subject: Re: [GENERAL] A way to let Vacuum warn if FSM settings
Previous:From: Tom LaneDate: 2005-03-14 06:35:38
Subject: Re: Question about accessing current row data inside trigger

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