From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | dmigowski(at)ikoffice(dot)de |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #10823: Better REINDEX syntax. |
Date: | 2014-07-30 16:07:50 |
Message-ID: | 20140730160750.GH2791@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Tue, Jul 1, 2014 at 10:33:07AM +0000, dmigowski(at)ikoffice(dot)de wrote:
> The following bug has been logged on the website:
>
> Bug reference: 10823
> Logged by: Daniel Migowski
> Email address: dmigowski(at)ikoffice(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-07-30 17:29:31 | Re: BUG #10823: Better REINDEX syntax. |
Previous Message | Peter Nelson | 2014-07-30 15:33:14 | extract('epoch' from age()) returning wrong number of seconds |
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2014-07-30 16:42:02 | Re: Distance from point to box |
Previous Message | Robert Haas | 2014-07-30 15:37:28 | Re: [w32] test_shm_mq test suite permanently burns connections slots |