| From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add important info about ANALYZE after create Functional Index |
| Date: | 2020-11-09 23:35:46 |
| Message-ID: | CAFcNs+p=T30HkfTTritZzWONbawrTpkd4gjyxAoPRMg-+O_iAg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 9 Nov 2020 at 20:27 Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> I see REINDEX CONCURRENTLY was fixed in head, but the docs didn't get
> updated to mention the need to run ANALYZE or wait for autovacuum before
> expression indexes can be fully used by the optimizer. Instead of
> putting this mention in the maintenance section, I thought the CREATE
> INDEX page make more sense, since it is more of a usability issue,
> rather than "why use expression indexes". Patch attached, which I plan
> to apply to all supported branches.
>
Did a quick review and totally agree... thanks a lot Bruce to help us don’t
miss it.
Regards,
--
Fabrízio de Royes Mello Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-11-09 23:49:04 | Re: Hybrid Hash/Nested Loop joins and caching results from subplans |
| Previous Message | Bruce Momjian | 2020-11-09 23:27:20 | Re: Add important info about ANALYZE after create Functional Index |