From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Henrik Zagerholm <henke(at)mac(dot)se>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: reindexdb command utlility |
Date: | 2006-08-22 01:02:23 |
Message-ID: | 200608220102.k7M12Os11560@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.
---------------------------------------------------------------------------
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 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/
[ Attachment, skipping... ]
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Sunil Kumar Basu | 2006-08-22 08:20:55 | BUG #2587: Connection problem |
Previous Message | Bruce Momjian | 2006-08-22 00:49:38 | Re: BUG #2467: Documentation |