| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "naman(dot)iitb" <naman(dot)bbps(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Creating Empty Index |
| Date: | 2013-11-02 23:28:05 |
| Message-ID: | CAB7nPqQpV1km2tU03ZyQzWiEVzmo3UQnEbC0-PcjE0_uJefoEg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 2, 2013 at 10:28 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> What exactly would be the point? Indexes are automatically maintained by
> postgres. Something that isn't doesn't seem to me to qualify for the
> description of "index".
Perhaps an index without data that could be used by the planner for
automatic query tuning to evaluate how a query could run if the index
exists? Like the concept of hypothetical indexes or something like the
possibility to do a CREATE/ALTER INDEX ... WITH [ NO ] DATA.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-11-02 23:45:02 | Re: [GENERAL] Cannot create matview when referencing another not-populated-yet matview in subquery |
| Previous Message | Andrew Dunstan | 2013-11-02 22:28:13 | Re: Creating Empty Index |