Re: BUG #10823: Better REINDEX syntax.

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: BUG #10823: Better REINDEX syntax.
Дата
Msg-id 20140730160750.GH2791@momjian.us
обсуждение исходный текст
Ответ на BUG #10823: Better REINDEX syntax.  (dmigowski@ikoffice.de)
Ответы Re: BUG #10823: Better REINDEX syntax.  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
On Tue, Jul  1, 2014 at 10:33:07AM +0000, dmigowski@ikoffice.de wrote:
> The following bug has been logged on the website:
>
> Bug reference:      10823
> Logged by:          Daniel Migowski
> Email address:      dmigowski@ikoffice.de
> PostgreSQL version: 9.1.13
> Operating system:   n/a
> Description:
>
> Hello.
>
> 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.

    REINDEX { INDEX | TABLE | DATABASE | SYSTEM } name [ FORCE ]
    ...
    name
           The name of the specific index, table, or database
           to be reindexed. Index and table names can be
           schema-qualified. Presently, REINDEX DATABASE and REINDEX SYSTEM
           can only reindex the current database, so their parameter must
           match the current database's name.

Let me look at improving that for 9.5.

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

  + Everyone has their own god. +

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [ADMIN] Can postgres run autovacuum tasks when autovacuum is disabled?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #10823: Better REINDEX syntax.