From: | Nicolas Paris <niparisco(at)gmail(dot)com> |
---|---|
To: | |
Cc: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: CREATE INDEX uses INDEX ? |
Date: | 2015-03-08 09:04:29 |
Message-ID: | CA+ssMOQbqeHTZu_Ja1EHypVf7KYwd_TjR+b9qW0vKP+LG=iqzw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Thanks.
Then,
Is it a good idea to run multiple instance of "create index on tableX" on
the same time ? Or is it better to do it sequentially ?
In other words : Can one seq scan on a table benefit to multiple create
index stmt on that table ?
Nicolas PARIS
2015-03-07 12:56 GMT+01:00 Guillaume Lelarge <guillaume(at)lelarge(dot)info>:
> Le 7 mars 2015 11:32, "Nicolas Paris" <niparisco(at)gmail(dot)com> a écrit :
> >
> > Hello,
> >
> > I wonder if the process of index creation can benefit from other indexes.
> >
>
> It cannot.
>
> > EG: Creating a partial index with predicat based on a boolean column,
> will use an hypothetic index on that boolean column or always use a seq
> scan on all rows ?
> >
>
> Nope, it always does a seqscan.
>
> > Goal is to create partial indexes faster.
> >
> > Explain command does not work with Create index.
> >
>
> You cannot use EXPLAIN on most DDL commands.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2015-03-08 09:09:15 | Re: CREATE INDEX uses INDEX ? |
Previous Message | Tomas Vondra | 2015-03-07 15:44:26 | Re: EXPLAIN (no ANALYZE) taking an hour for INSERT FROM SELECT |