Re: BUG #10823: Better REINDEX syntax. - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #10823: Better REINDEX syntax.
Date
Msg-id 20140730173555.GI2791@momjian.us
Whole thread Raw
In response to Re: BUG #10823: Better REINDEX syntax.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #10823: Better REINDEX syntax.  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: BUG #10823: Better REINDEX syntax.  (Vik Fearing <vik.fearing@dalibo.com>)
List pgsql-bugs
On Wed, Jul 30, 2014 at 01:29:31PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Tue, Jul  1, 2014 at 10:33:07AM +0000, dmigowski@ikoffice.de wrote:
> >> Compared to CLUSTER and VACUUM FULL we need to specify a database to the
> >> REINDEX command. Why? It would be logical to reindex the current database,
> >> exactly like CLUSTER does. So why isn't the DATABASE parameter optional?
>
> > Wow, yeah, that is kind of odd, e.g.
>
> I don't find it all that odd.  We should not be encouraging routine
> database-wide reindexes.

Uh, do we encourage database-wide VACUUM FULL or CLUSTER, as we use them
there with no parameter.  Is there a reason REINDEX should be harder,
and require a dummy argument to run?

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +

pgsql-bugs by date:

Previous
From: Peter Nelson
Date:
Subject: extract('epoch' from age()) returning wrong number of seconds
Next
From: Tom Lane
Date:
Subject: Re: BUG #10823: Better REINDEX syntax.