Bruce Momjian pgman@candle.pha.pa.us writes:
These new messages:
NOTICE: max_fsm_relations(1000) equals the number of relations checked
HINT: You have = 44 relations.
Consider increasing the configuration parameter max_fsm_relations.
NOTICE: the number of
Ron Mayer wrote:
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.
You will probably see the creation of indexes and sequences, like this:
test=
Bruce Momjian pgman@candle.pha.pa.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_
Well, I was really hoping something would end up in the log file.
The situation is that our clients - sometimes not that computer
savvy - go perhaps a year without us being involved (unless
the log monitoring scripts show something abnormal; or if the
system breaks).
The primary motivation for
Ron Mayer wrote:
Well, I was really hoping something would end up in the log file.
The situation is that our clients - sometimes not that computer
savvy - go perhaps a year without us being involved (unless
the log monitoring scripts show something abnormal; or if the
system breaks).
The
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
I have applied your patch with minor modifications. Applied version
attached.
I think the pages message:
INFO: free space map: 44 relations, 28 pages stored; 704 total pages
used
DETAIL: FSM size: 1000 relations + 2 pages = 182 kB shared memory.
should remain
[ Previous version removed.]
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.