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
> messages as INFO when VERBOSE was used. But it doesn't (and this is
> not a request to add one). Without VERBOSE, I think it's utterly
> unacceptable to force the messages out regardless of client_min_messages.
> NOTICE was a reasonable level, maybe LOG would be a better one. But
> not INFO.
>
LOG would be a good option, but maybe a small hack in reindexdb is
better.
--
Euler Taveira de Oliveira
http://www.timbira.com/
Index: src/bin/scripts/reindexdb.c
===================================================================
RCS file: /projects/cvsroot/pgsql/src/bin/scripts/reindexdb.c,v
retrieving revision 1.5
diff -c -r1.5 reindexdb.c
*** src/bin/scripts/reindexdb.c 5 Mar 2006 15:58:52 -0000 1.5
--- src/bin/scripts/reindexdb.c 8 Jun 2006 00:42:44 -0000
***************
*** 229,234 ****
--- 229,241 ----
conn = connectDatabase(dbname, host, port, username, password,
progname);
+ /* Suppress some NOTICE messages from REINDEX command */
+ if (quiet)
+ {
+ result = PQexec(conn, "SET client_min_messages = warning");
+ PQclear(result);
+ }
+
if (echo)
printf("%s", sql.data);
result = PQexec(conn, sql.data);
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
