Re: Clarification on the docs
Igor Korot <ikorot01@gmail.com>
From: Igor Korot <ikorot01@gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2025-04-12T03:08:48Z
Lists: pgsql-general
Hi, David, On Fri, Apr 11, 2025 at 9:04 PM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Fri, Apr 11, 2025 at 6:49 PM Igor Korot <ikorot01@gmail.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 > This above looks much better. What stops you from pushing it? There is no double meaning and everything is split nicely. Thank you. David J. > >
Commits
-
Doc: do a little copy-editing on Index Storage Parameters list.
- 78637a8be20e 18.0 landed