On Mon, 2005-03-14 at 01:40 -0500, Tom Lane wrote:
> 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.
Personally, I prefer the postmaster log as the place for this.
However, whilst vacuum exists as a separate command, there will be an
argument to return a message back to the person running it; we cannot
assume that people would be inattentive.
Possibly the deciding factor should be whether autovacuum makes it fully
into becoming a special backend anytime soon, since in that case only
the log would remain as an option for reporting this message, in that
Can we have both?
Best Regards, Simon Riggs
In response to
pgsql-patches by date
|Next:||From: Andre Maasikas||Date: 2005-03-14 11:11:58|
|Subject: Re: CC Date format code defaults to current centry|
|Previous:||From: Christopher Kings-Lynne||Date: 2005-03-14 07:46:34|
|Subject: Sort psql output|
pgsql-general by date
|Next:||From: Janning Vygen||Date: 2005-03-14 08:21:39|
|Subject: Re: normal user dump gives error because of plpgsql|
|Previous:||From: Tom Lane||Date: 2005-03-14 06:40:02|
|Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low. [final?] |