|From:||Bruce Momjian <bruce(at)momjian(dot)us>|
|To:||Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>|
|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|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Mon, Nov 9, 2020 at 08:35:46PM -0300, Fabrízio de Royes Mello wrote:
> 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.
Patch applied to all branches. Thanks for the review.
The usefulness of a cup is in its emptiness, Bruce Lee
|Next Message||e.sokolova||2020-11-12 20:10:05||Re: [PATCH] Add extra statistics to explain for Nested Loop|
|Previous Message||Bruce Momjian||2020-11-12 19:36:22||Re: Aw: Re: Minor documentation error regarding streaming replication protocol|