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

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

From: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
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>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,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-13 06:11:44
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-patches
Bruce Momjian wrote:
> You didn't like server_min_messages = 'notify'?

I merely don't have a feeling for how much additional stuff
verbose would be putting in the log files.

If it's a good practice for production systems to be logging
NOTIFY's I'm happy with the change.

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.

Also since the message happing occasionally is probably OK,
yet if it happens a lot it's more likely worth looking
into - I think the historical record of when it happened
is more interesting than a one-time occurrence which is
all you seen in the active session.


PS: I'm fine either way; and perhaps it's a good idea
for me to be logging NOTIFY's anyway -- I just thought
I'd explain my reasoning above.  I'm sure you guys know
a lot more than me what best practices would be.

In response to


pgsql-patches by date

Next:From: Marko KreenDate: 2005-03-13 09:12:53
Subject: Re: pgcrypto: openssl digest fix
Previous:From: Bruce MomjianDate: 2005-03-13 05:42:11
Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low. [final?]

pgsql-general by date

Next:From: Peter EisentrautDate: 2005-03-13 11:13:38
Subject: Re: General query optimization howto
Previous:From: Russell SmithDate: 2005-03-13 06:11:34
Subject: Re: Using sequence name depending on other column

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