From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Igor Korot <ikorot01(at)gmail(dot)com> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Clarification on the docs |
Date: | 2025-04-12 02:03:38 |
Message-ID: | CAKFQuwZrL59BXqZB8c1x-dsUwSunDO=D39+kra0z+JraVcV6+Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Apr 11, 2025 at 6:49 PM Igor Korot <ikorot01(at)gmail(dot)com> wrote:
> Hi, ALL,
> On the
> https://www.postgresql.org/docs/17/sql-createindex.html#SQL-CREATEINDEX-STORAGE-PARAMETERS
> its said:
>
> [quote]
> The optional WITH clause specifies storage parameters for the index.
> Each index method has its own set of allowed storage parameters. The
> B-tree, hash, GiST and SP-GiST index methods all accept this
> parameter:
> [/quote]
>
>
These are the index methods and the valid lists for each. The docs are
correct in how they remove duplication. I'm undecided on whether that is
the best presentation choice. I would at minimum place a new paragraph
after "own set of allowed storage parameters." so that "The B-tree,
hash..." begins its own line.
B-tree:
fillfactor
deduplicate_items
Hash:
fillfactor
Gist:
fillfactor
buffering
SP-Gist:
fillfactor
GIN:
fastupdate
gin_pending_list_limit
BRIN:
pages_per_range
autosummarize
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Korot | 2025-04-12 03:08:48 | Re: Clarification on the docs |
Previous Message | Igor Korot | 2025-04-12 01:48:55 | Clarification on the docs |