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

Re: reindexdb command utlility

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Your patch has been added to the PostgreSQL unapplied patches list at:

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

[ Attachment, skipping... ]

> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?

  Bruce Momjian   bruce(at)momjian(dot)us

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-bugs by date

Next:From: Sunil Kumar BasuDate: 2006-08-22 08:20:55
Subject: BUG #2587: Connection problem
Previous:From: Bruce MomjianDate: 2006-08-22 00:49:38
Subject: Re: BUG #2467: Documentation

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