| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | dinesh kumar <dineshkumar02(at)gmail(dot)com> |
| Cc: | AI Rumman <rummandba(at)gmail(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: when do I analyze after concurrent index creation? |
| Date: | 2013-10-18 15:42:50 |
| Message-ID: | 8902.1382110970@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
dinesh kumar <dineshkumar02(at)gmail(dot)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.
Whether you used CREATE INDEX CONCURRENTLY or some other way of creating
the index doesn't matter at all.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rémi Cura | 2013-10-18 15:49:17 | Re: Cannot import logs from csv |
| Previous Message | Rion Massie | 2013-10-18 15:36:04 | Re: Cannot import logs from csv |