agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedFrom: Egor Rogov <e.rogov@postgrespro.ru>
To: pgsql-docs@lists.postgresql.org
Subject: Parallel index build for BRIN
Date: Tue, 5 Nov 2024 12:12:14 +0300
Message-ID: <114e2d5d-125e-07d8-94aa-5ad175fb7443@postgrespro.ru> (raw)
Hi,
Commit b4375717 introduced parallel CREATE INDEX for BRIN. I've noticed
that a couple of documentation pages need to be updated accordingly. A
small patch is attached.
Thanks,
Egor
From 50dd542f113b915d52f47347efb6d7835bc6bb40 Mon Sep 17 00:00:00 2001
From: Egor Rogov <e.rogov@postgrespro.ru>
Date: Tue, 5 Nov 2024 11:52:15 +0300
Subject: [PATCH] Doc: parallel CREATE INDEX is allowed for BRIN
Commit b4375717 introduced parallel index build for BRIN,
but missed updating the documentation about it.
---
doc/src/sgml/config.sgml | 2 +-
doc/src/sgml/ref/create_index.sgml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index d54f9049569..b5b1580dee7 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2835,7 +2835,7 @@ include_dir 'conf.d'
Sets the maximum number of parallel workers that can be
started by a single utility command. Currently, the parallel
utility commands that support the use of parallel workers are
- <command>CREATE INDEX</command> only when building a B-tree index,
+ <command>CREATE INDEX</command> when building a B-tree or BRIN index,
and <command>VACUUM</command> without <literal>FULL</literal>
option. Parallel workers are taken from the pool of processes
established by <xref linkend="guc-max-worker-processes"/>, limited
diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 621bc0e253c..208389e8006 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -808,7 +808,7 @@ Indexes:
leveraging multiple CPUs in order to process the table rows faster.
This feature is known as <firstterm>parallel index
build</firstterm>. For index methods that support building indexes
- in parallel (currently, only B-tree),
+ in parallel (currently, B-tree and BRIN),
<varname>maintenance_work_mem</varname> specifies the maximum
amount of memory that can be used by each index build operation as
a whole, regardless of how many worker processes were started.
--
2.37.1 (Apple Git-137.1)
Attachments:
[text/plain] 0001-Doc-parallel-CREATE-INDEX-is-allowed-for-BRIN.patch (2.0K, ../114e2d5d-125e-07d8-94aa-5ad175fb7443@postgrespro.ru/2-0001-Doc-parallel-CREATE-INDEX-is-allowed-for-BRIN.patch)
download | inline diff:
From 50dd542f113b915d52f47347efb6d7835bc6bb40 Mon Sep 17 00:00:00 2001
From: Egor Rogov <e.rogov@postgrespro.ru>
Date: Tue, 5 Nov 2024 11:52:15 +0300
Subject: [PATCH] Doc: parallel CREATE INDEX is allowed for BRIN
Commit b4375717 introduced parallel index build for BRIN,
but missed updating the documentation about it.
---
doc/src/sgml/config.sgml | 2 +-
doc/src/sgml/ref/create_index.sgml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index d54f9049569..b5b1580dee7 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2835,7 +2835,7 @@ include_dir 'conf.d'
Sets the maximum number of parallel workers that can be
started by a single utility command. Currently, the parallel
utility commands that support the use of parallel workers are
- <command>CREATE INDEX</command> only when building a B-tree index,
+ <command>CREATE INDEX</command> when building a B-tree or BRIN index,
and <command>VACUUM</command> without <literal>FULL</literal>
option. Parallel workers are taken from the pool of processes
established by <xref linkend="guc-max-worker-processes"/>, limited
diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 621bc0e253c..208389e8006 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -808,7 +808,7 @@ Indexes:
leveraging multiple CPUs in order to process the table rows faster.
This feature is known as <firstterm>parallel index
build</firstterm>. For index methods that support building indexes
- in parallel (currently, only B-tree),
+ in parallel (currently, B-tree and BRIN),
<varname>maintenance_work_mem</varname> specifies the maximum
amount of memory that can be used by each index build operation as
a whole, regardless of how many worker processes were started.
--
2.37.1 (Apple Git-137.1)
view thread (7+ messages) latest in thread
Message-ID: <114e2d5d-125e-07d8-94aa-5ad175fb7443@postgrespro.ru>
Permalink: ../114e2d5d-125e-07d8-94aa-5ad175fb7443@postgrespro.ru/
Also on: postgresql.org/message-id/114e2d5d-125e-07d8-94aa-5ad175fb7443@postgrespro.ru
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: e.rogov@postgrespro.ru, pgsql-docs@lists.postgresql.org
Subject: Re: Parallel index build for BRIN
In-Reply-To: <114e2d5d-125e-07d8-94aa-5ad175fb7443@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox