pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: galiev_mr@taximaxim.ru
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: INDEX with optional storage parameter value
Date: Tue, 30 Jun 2020 12:28:07 -0400
Message-ID: <20200630162807.GC28710@momjian.us> (raw)
In-Reply-To: <218a622abfb0aa895e9fce4e41b278e469932211.camel@cybertec.at>
References: <159283163235.684.4482737698910467437@wrigleys.postgresql.org>
	<20200627211423.GG16644@momjian.us>
	<218a622abfb0aa895e9fce4e41b278e469932211.camel@cybertec.at>

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






view thread (7+ messages)  latest in thread

Message-ID: <20200630162807.GC28710@momjian.us>
Permalink:  ../20200630162807.GC28710@momjian.us/
Also on:    postgresql.org/message-id/20200630162807.GC28710@momjian.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: bruce@momjian.us, laurenz.albe@cybertec.at, galiev_mr@taximaxim.ru, pgsql-docs@lists.postgresql.org
  Subject: Re: INDEX with optional storage parameter value
  In-Reply-To: <20200630162807.GC28710@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox