Date: Thu, 12 Nov 2020 15:01:10 -0500
From: Bruce Momjian <bruce@momjian.us>
To: =?iso-8859-1?Q?Fabr=EDzio?= de Royes Mello <fabriziomello@gmail.com>
Cc: Nikolay Samokhvalov <samokhvalov@gmail.com>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Add important info about ANALYZE after create Functional Index
Message-ID: <20201112200110.GC4506@momjian.us>
References: 
 <CAFcNs+qpFPmiHd1oTXvcPdvAHicJDA9qBUSujgAhUMJyUMb+SA@mail.gmail.com>
 <CANNMO++5rw9RDA=p40iMVbMNPaW6O=S0AFzTU=KpYHRpCd1voA@mail.gmail.com>
 <20201109232720.GA8930@momjian.us>
 <CAFcNs+p=T30HkfTTritZzWONbawrTpkd4gjyxAoPRMg-+O_iAg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAFcNs+p=T30HkfTTritZzWONbawrTpkd4gjyxAoPRMg-+O_iAg@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

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@momjian.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.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee