Re: when do I analyze after concurrent index creation? - Mailing list pgsql-general

From dinesh kumar
Subject Re: when do I analyze after concurrent index creation?
Date
Msg-id CALnrH7ow=O_-JFwerWpSBHxnU6rM11xNRVdX0==Wz9J-ihHfgw@mail.gmail.com
Whole thread Raw
In response to Re: when do I analyze after concurrent index creation?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Fri, Oct 18, 2013 at 9:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
dinesh kumar <dineshkumar02@gmail.com> writes:
> When we create an index, i believe the postgres engine it self update it's
> catalog about the index availability.

ANALYZE normally collects statistics about the contents of table columns.
Thus, adding (or removing) an index does not create any reason to
re-ANALYZE.

However ... if you have an index on an expression (not just a simple
column value), that cues ANALYZE to collect statistics about the values of
that expression.  So re-analyzing is useful after creating such an index,
to give the planner a better idea of when to use that index.


Thank you Tom.
 
Whether you used CREATE INDEX CONCURRENTLY or some other way of creating
the index doesn't matter at all.

                        regards, tom lane

Regards,
Dinesh

pgsql-general by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Preserving the source code of views
Next
From: Ken Tanzer
Date:
Subject: pg_dump doesn't restore on newer database due to schema issues (bug or limitation?)