Date: Tue, 30 Jun 2020 12:28:07 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: galiev_mr@taximaxim.ru, pgsql-docs@lists.postgresql.org
Subject: Re: INDEX with optional storage parameter value
Message-ID: <20200630162807.GC28710@momjian.us>
References: <159283163235.684.4482737698910467437@wrigleys.postgresql.org>
 <20200627211423.GG16644@momjian.us>
 <218a622abfb0aa895e9fce4e41b278e469932211.camel@cybertec.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <218a622abfb0aa895e9fce4e41b278e469932211.camel@cybertec.at>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Mon, Jun 29, 2020 at 09:26:57AM +0200, Laurenz Albe wrote:
> On Sat, 2020-06-27 at 17:14 -0400, Bruce Momjian wrote:
> > > I noticed an slight inaccuracy in the documentation for CREATE INDEX and
> > > ALTER INDEX:
> > > 
> > > CREATE INDEX ... [ WITH ( storage_parameter = value [, ... ] ) ]
> > > ALTER INDEX [ IF EXISTS ] name SET ( storage_parameter = value [, ... ] )
> > > 
> > > In indices, as in tables, you can omit the вoolean value for a parameter.
> > > For example:
> > > 
> > > CREATE INDEX ON public.testtable USING GIN (c1) WITH (fastupdate);
> > > ALTER INDEX testtable_c1_idx SET (fastupdate);
> > > 
> > > It might be more correct to use the construct from CREATE TABLE: 
> > > 
> > > storage_parameter [= value] [, ... ]
> > 
> > I found a few more places that also didn't properly document this; 
> > patch attached.
> 
> Looks good.
> Perhaps it is worth explaining this explicitly, as in the attached.

Uh, I considered this, but it seems unnecessary at this time.

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

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