| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | galiev_mr(at)taximaxim(dot)ru, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: INDEX with optional storage parameter value |
| Date: | 2020-06-30 16:28:07 |
| Message-ID: | 20200630162807.GC28710@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-06-30 16:28:23 | Re: INDEX with optional storage parameter value |
| Previous Message | Fujii Masao | 2020-06-30 05:56:50 | Re: The description for pg_replication_slots.restart_lsn |