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 1u3QFD-00FWLy-Uc for pgsql-general@arkaria.postgresql.org; Sat, 12 Apr 2025 02:05:20 +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 1u3QEE-00H9kA-1y for pgsql-general@arkaria.postgresql.org; Sat, 12 Apr 2025 02:04:18 +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 1u3QED-00H9k2-JJ for pgsql-general@lists.postgresql.org; Sat, 12 Apr 2025 02:04:18 +0000 Received: from mail-oa1-x32.google.com ([2001:4860:4864:20::32]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u3QEC-004OqH-07 for pgsql-general@lists.postgresql.org; Sat, 12 Apr 2025 02:04:17 +0000 Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-2c2ada8264aso1316389fac.2 for ; Fri, 11 Apr 2025 19:04:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744423455; x=1745028255; 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=Rtc7VlvnKDRmnrgt6dZK3Qa2ZfmKZi01oINyRC2YoCM=; b=SSkvz18vokPWCt8lwLDlPLTuNbXyXyO2NKm3xO7dP+8R5M7s0uCZTX79b1QaDfHIXy M/EVyopUKpGFqFpNxN7bNqbYnqnhaHg/8oTm0qjGAkMd5cMlHvB7eKxjItfXzy4ga26f xt4KmjhK7ps32Q3NOYKI33Pn/Sfs5iYNPOlRXJQhqCe2Wkcm4gx6q3i8uRFPHe8pkEhW 4IkfAtIG1VIiQoXR+YDqzusNJasNycwJcHlb/JIM+fa0LVY0CEQmXGjjyOQWz115AWn8 3hAEIePFvDwB9yUSu/eJaIscpVAKh0h4BcFWh9RjOSOvCpFObEbNWJ1Sg1/5IuTj6JWH KrBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744423455; x=1745028255; 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=Rtc7VlvnKDRmnrgt6dZK3Qa2ZfmKZi01oINyRC2YoCM=; b=n3n13gBaWtUk15UoTsoxe9U0OOrPndIRkXMNwyW0dT9ByExJxZ9lURSHO9fLQzcpYR ZxxeiICLfYDHomf3ffXa7GKBnOuKjTFquqDbHhyiOzeGm0KZybFfmlRbovQnrCftM2GG fIy2VgXJD58aLUmJI9VSpLJO6n+T7jQUpTaYkBPg7qaeq6x8HWZBueObPvy9VijnhZfy WVPEexx0hDNDZLis0JCkGZJQLMmBJ9avNLoNe+VpfV4DWoqSYcyQ8/EcUjmZOuyCZFxW C9efS0IJPOj3yQMe+vq5qwl7ZLf315vvuqPBABIyCNtdrxTeBmDBsg5TkVGkPwmTFv73 6lGg== X-Gm-Message-State: AOJu0YzTD6RkYYhXzo8Jfd9V/7oPAAs+zsdWOEdp1Jo/PWMcN5wJ4bbf 9//Amf8rFPCYovV4JeH9GyHDEleLLI1H7zrPkXBdanqaSWWWrhqi/NCftEbZrG2IXrUpGbSH8Hr jpPhXReaIIgsoLq2PJRg5XKv8vYg= X-Gm-Gg: ASbGncv2Q3W6GRX4ALNQ6OwFwomBZwWu9ivlMwz3eB1YTMe7NpVwtZ28gTIHXH6OSs8 /a6csYu9JG4ZShB4ZjgyvR0nD993rlMdx47/NOCc747NVTs2A7srj5FsFFE7FxIgLC50roMok7c cgaD5kR9zTBqtaw+A+sYym X-Google-Smtp-Source: AGHT+IEgQkjO3L1gQkSW7oJ8auFkplSPli3u9d4k1/8Mh6TvhtIl+TrExrLVAiWWmOCd7R1gq5oZS9hKwtvk1rUtsKk= X-Received: by 2002:a05:6871:a509:b0:2c2:544d:e140 with SMTP id 586e51a60fabf-2d0d5c77939mr2919001fac.11.1744423455086; Fri, 11 Apr 2025 19:04:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Fri, 11 Apr 2025 19:03:38 -0700 X-Gm-Features: ATxdqUEhdqeCljl-c1SNRtzV3slrQCMPLgMwAPiqS3Nkf0n8gYYVQCU0f_p9O2M Message-ID: Subject: Re: Clarification on the docs To: Igor Korot Cc: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000060e0c206328b3c78" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000060e0c206328b3c78 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Apr 11, 2025 at 6:49=E2=80=AFPM Igor Korot wro= te: > Hi, ALL, > On the > https://www.postgresql.org/docs/17/sql-createindex.html#SQL-CREATEINDEX-S= TORAGE-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. --00000000000060e0c206328b3c78 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Apr 11, 2025 at 6:49=E2=80=AFPM Igor Korot <ikorot01@gmail.com> wrote:=
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

David J.

--00000000000060e0c206328b3c78--