| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal : REINDEX SCHEMA |
| Date: | 2014-10-12 17:27:25 |
| Message-ID: | 20141012172725.GX28859@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> Sawada Masahiko wrote:
> > Attached WIP patch adds new syntax REINEX SCHEMA which does reindexing
> > all table of specified schema.
> > There are syntax dose reindexing specified index, per table and per database,
> > but we can not do reindexing per schema for now.
>
> It seems doubtful that there really is much use for this feature, but if
> there is, I think a better syntax precedent is the new ALTER TABLE ALL
> IN TABLESPACE thingy, rather than your proposed REINDEX SCHEMA.
> Something like REINDEX TABLE ALL IN SCHEMA perhaps.
Yeah, I tend to agree that we should be looking at the 'ALL IN
TABLESPACE' and 'ALL IN SCHEMA' type of commands to keep things
consistent. This might be an alternative for the vacuum / analyze /
reindex database commands also..
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Flower | 2014-10-12 20:09:36 | Re: Column Redaction |
| Previous Message | Tom Lane | 2014-10-12 15:55:21 | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) |