Re: [BUGS] reindexdb command utlility

2006-09-01 Thread Bruce Momjian
Patch applied. Thanks. --- Euler Taveira de Oliveira wrote: > Tom Lane wrote: > > > Yeah, *only because you said VERBOSE*. When we implemented the current > > elog level scheme, we designed INFO as non-suppressible so th

Re: [BUGS] reindexdb command utlility

2006-08-21 Thread Bruce Momjian
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. --- Eu

Re: [BUGS] reindexdb command utlility

2006-06-07 Thread Euler Taveira de Oliveira
Tom Lane wrote: > Yeah, *only because you said VERBOSE*. When we implemented the current > elog level scheme, we designed INFO as non-suppressible so that it would > mimic the previous behavior of VACUUM VERBOSE. > Agreed. > If REINDEX had a VERBOSE option, it would make sense to put out the >

Re: [BUGS] reindexdb command utlility

2006-06-07 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian writes: > > I thought it needed changing for consistency. Shouldn't status messages > > like this be INFO: > > test=> REINDEX DATABASE test; > > NOTICE: table "pg_class" was reindexed > > > If I do VACUUM VERBOSE, those messages are INFO. > > Yeah, *only

Re: [BUGS] reindexdb command utlility

2006-06-07 Thread Tom Lane
Bruce Momjian writes: > I thought it needed changing for consistency. Shouldn't status messages > like this be INFO: > test=> REINDEX DATABASE test; > NOTICE: table "pg_class" was reindexed > If I do VACUUM VERBOSE, those messages are INFO. Yeah, *only because you said VERBOSE*. W

Re: [BUGS] reindexdb command utlility

2006-06-07 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian writes: > > Patch applied. Thanks. > > Why is this an improvement? AFAIR an INFO message is *not suppressible* > by adjusting client_min_messages, therefore this makes the system more > chatty not less so. It certainly doesn't do anything to address the > origin

Re: [BUGS] reindexdb command utlility

2006-06-07 Thread Tom Lane
Bruce Momjian writes: > Patch applied. Thanks. Why is this an improvement? AFAIR an INFO message is *not suppressible* by adjusting client_min_messages, therefore this makes the system more chatty not less so. It certainly doesn't do anything to address the original complaint.

Re: [BUGS] reindexdb command utlility

2006-06-07 Thread Bruce Momjian
Patch applied. Thanks. --- Euler Taveira de Oliveira wrote: > > I used wanted to point out the the ( -q, --quiet ) parameter for > > reindexdb command utility does not work. > Actually it is *not* a bug. The NOTICE is pr

Re: [BUGS] reindexdb command utlility

2006-05-31 Thread Euler Taveira de Oliveira
Henrik Zagerholm wrote: > >You can always ignore NOTICE. grep is your friend. :-) > True, but usually I like to have my ERROR messages to stderr and INFO > to stdout. > But it's not true in PostgreSQL. All ereport() messages are sent to stderr. In some scripts, the -e (echo) is used to print co

Re: [BUGS] reindexdb command utlility

2006-05-31 Thread Henrik Zagerholm
31 maj 2006 kl. 03:47 skrev Euler Taveira de Oliveira: I used wanted to point out the the ( -q, --quiet ) parameter for reindexdb command utility does not work. Actually it is *not* a bug. The NOTICE is printed by the REINDEX command; reindexdb is just a wrapper around REINDEX command. If you

Re: [BUGS] reindexdb command utlility

2006-05-30 Thread Euler Taveira de Oliveira
> I used wanted to point out the the ( -q, --quiet ) parameter for > reindexdb command utility does not work. Actually it is *not* a bug. The NOTICE is printed by the REINDEX command; reindexdb is just a wrapper around REINDEX command. If you set up 'client_min_messages' in postgresql.conf, you d