Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u3REt-00Fmgb-Io for pgsql-general@arkaria.postgresql.org; Sat, 12 Apr 2025 03:09:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u3REs-000BTf-0M for pgsql-general@arkaria.postgresql.org; Sat, 12 Apr 2025 03:09:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u3REr-000BTX-Gp for pgsql-general@lists.postgresql.org; Sat, 12 Apr 2025 03:09:01 +0000 Received: from mail-yw1-x1132.google.com ([2607:f8b0:4864:20::1132]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u3REp-004PGO-2v for pgsql-general@lists.postgresql.org; Sat, 12 Apr 2025 03:09:00 +0000 Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-6fee50bfea5so22454767b3.1 for ; Fri, 11 Apr 2025 20:08:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744427339; x=1745032139; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6dhGcExlK8B/j1aMFMNsNnWZ8VL8MTnwBHnnfz7GaJQ=; b=Zz97BMPCPzDUNTUXRyMBGsnRoQNocWxfxSc2XncR8FL28H+8FEv6/52liW/9RIyun2 xjj8utsRcqObPsM871KrNHbjJ/WiSR4WarQpfxYP/ZL8JH8opbXAhFCjdIA0K/Bv+mhe vQ3GZ6Zv+DVBgPY1YclZWm4md1Yc+qnLjkgR5ciXsjwP4Xoj3bXZU4cwJrWFt//5tobT F/Q1AP4M6MMp0cefoRHNxc+QqOe2YRSp16fSytjfUV2YO+kwKeimrLNAJ5lntMUj93n6 CCGpnZaqd9T3U+hSES3FN36V9+D5qCsK4UL4pBooPRVqqRA/gBe+ta//22aRT/+fyJEe oNrw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744427339; x=1745032139; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=6dhGcExlK8B/j1aMFMNsNnWZ8VL8MTnwBHnnfz7GaJQ=; b=wAIp4ZiW4wvmTOqXAfLoMR2NtO4E65B/pq8y3PI1RBlOB5GaGqyNJEdISICsab47Na vk1hAwEv7epDdhAtTcOpch4T3roR//5L7us9yfSPlG/RYCOxscrr2yXPOOpPFrKHFUE7 pXV8D3DQ5e3Y4CbpIhhBzZ/5z0M9HdscPR9loGFZlmvInZMMK0XXoZLy8MfOqTj4PWdn eBDVHQukzDuqe8cp0nGw17eEBwsGLiESYImc0meYcZ0azckpzcqRZh1K09FSKg/xY/hb BoCcnzpEpYTxTUHnwa0OXWZ9z0IVFNszH138kxz/CMV0SBO/afVTF20QxjUWrVfp3cCT K/kg== X-Gm-Message-State: AOJu0Yzy3VgjfCaD/0HXqUUBILcHz1fdCfe0GaqBmuPVT212YR1PlMED 4aQEfMy5Aj6R0ElMl9SklfDuru9/+57EjB73wKwvxgo0e3koSrkQNZeh9VkjAy6PVfdcjdfPjs1 XHGnfsLVLm/I2ykiS7eRbiEGQFas= X-Gm-Gg: ASbGnctb0V92EAoZNNoptB5oZ4u0NH8VIenaHLJTPyJM5YiiALlnd4Qt5a2WKxgIhOV WCs87DiikKeHRYgsUTxvqRhrPBVY9nuR0F6ub/IVjRDfS7ISqTREZ7eixAkH3qiWcW8LXHgSZBO wOBZGkCYPMcDaMwZKGWsIcj47pwTM7tE1f096jyjHoy9f2lR1/6FWpAR4= X-Google-Smtp-Source: AGHT+IEUl2gIVeGghjJ3ny2Cs2ZZ3Sh5oKvgR9fMxKPd1sK3PIvVq9WLflpYpXYzCMfyqe1F2eqtFKUenPRvDOkL8Xc= X-Received: by 2002:a05:690c:25c5:b0:6f9:776f:71d7 with SMTP id 00721157ae682-705599f9efamr86518937b3.21.1744427338838; Fri, 11 Apr 2025 20:08:58 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Igor Korot Date: Fri, 11 Apr 2025 22:08:48 -0500 X-Gm-Features: ATxdqUFY4TFxbF7Wac2rMfH4TFeT3nCCwp55Decnhe10P2_O7b51zC5oNBEVLUQ Message-ID: Subject: Re: Clarification on the docs To: "David G. Johnston" Cc: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000de3af406328c23e0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000de3af406328c23e0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, David, On Fri, Apr 11, 2025 at 9:04=E2=80=AFPM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Fri, Apr 11, 2025 at 6:49=E2=80=AFPM Igor Korot w= rote: > >> 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. > > --000000000000de3af406328c23e0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi, David,

On Fri, Apr 11, 2025= at 9:04=E2=80=AFPM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Fri, Apr 11, 2025 at 6:49=E2=80=AFPM Igor Korot = <ikorot01@gmail.com> wrote:<= /div>
Hi, ALL,
On the htt= ps://www.postgresql.org/docs/17/sql-createindex.html#SQL-CREATEINDEX-STORAG= E-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.=C2=A0 The docs are correct in how they remove= duplication.=C2=A0 I'm undecided on whether that is the best presentat= ion choice.=C2=A0 I would at minimum place a new paragraph after "own = set of allowed storage parameters." so that "The B-tree, hash...&= quot; begins its own line.

B-tree:
fillfac= tor
deduplicate_items

Hash:
fillfactor=

Gist:
fillfactor
buffering
SP-Gist:
fillfactor

GIN:
fa= stupdate
gin_pending_list_limit

BRIN:
= pages_per_range
autosummarize

This above looks much better. What s= tops you from pushing it?

There is no double meaning and everything is split nicely.

Thank you.

David J.

<= /div>
--000000000000de3af406328c23e0--