| 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: | 5671.1110782402@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2005-03-14 08:17:48 | Re: [GENERAL] A way to let Vacuum warn if FSM settings |
| Previous Message | Tom Lane | 2005-03-14 06:35:38 | Re: Question about accessing current row data inside trigger |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2005-03-14 06:42:07 | [david@fetter.org: Clean up SGML for openjade] |
| Previous Message | David Fetter | 2005-03-14 06:23:19 | Clean up SGML for openjade |