From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Index recreation details with REINDEX TABLE CONCURRENTLY
Date: Wed, 10 May 2023 15:36:02 -0500
Message-ID: <5ec087d5-e07c-e704-96cd-a3f8fb9f91d7@gmail.com> (raw)
In-Reply-To: <87ild0p6d4.fsf@gmail.com>
References: <87ild0p6d4.fsf@gmail.com>
On 5/10/23 10:04, Matthew Planchard wrote:
> Hello,
>
> We're working on setting up some regular jobs to reindex tables where we
> wind up generating a lot of index bloat. We're planning on using REINDEX
> ... CONCURRENTLY. We'd like to reindex all of the indexes on the tables.
>
> In some of our environments, these tables are very large and under high
> load, and we want to minimize the resource consumption of index
> recreation if possible.
>
> With that in mind, my question is: does REINDEX TABLE CONCURRENTLY
> operate on the indexes of the table in parallel, or sequentially? If
> in parallel, I imagine we would see less DB resource utilization by
> updating one index at a time.
https://www.postgresql.org/docs/11/sql-createindex.html
The CREATE INDEX page certainly mentions parallel index builds. It would
definitely be very good to know whether REINDEX TABLE CONCURRENTLY can have
multiple "threads" leveraging table data already in cache so as not to have
to reread the whole table each time.
That (concurrent CREATE INDEX statements) really sped things up Back In The
Day).
--
Born in Arizona, moved to Babylonia.
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-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Index recreation details with REINDEX TABLE CONCURRENTLY
In-Reply-To: <5ec087d5-e07c-e704-96cd-a3f8fb9f91d7@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox