From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Feature Request: multithreaded reindexdb --concurrently of a single table |
Date: | 2025-02-22 00:03:06 |
Message-ID: | CANzqJaDbob-nHc+pAu-mvb+WuXd4Dehe3atwqktq+nUbTG325Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, Feb 21, 2025 at 1:46 PM Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:
> On 2025-Feb-18, Ron Johnson wrote:
>
> > It would be really really handy to be able to run multiple REINDEX INDEX
> > jobs at the same time, either by just specifying the table as above and
> > reindexdb automagically getting the index names, or by manually
> enumerating
> > each index, and then see all four REINDEX INDEX statements in
> > pg_stat_activity.
>
> I don't think multiple REINDEX commands can run concurrently on the same
> table, so this is not a reindexdb issue but a server issue. And TBH I
> think the server feature to support that is not likely to be implemented
> soon.
>
That's a shame. Big server, lots of RAM, lots of CPUs, a big table, and
lots of indices just begs for concurrently running REINDEX / CREATE INDEX
statements on the same table.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
From | Date | Subject | |
---|---|---|---|
Next Message | Gambhir Singh | 2025-02-23 05:56:10 | Changing the Datatype from Bit to Boolean. |
Previous Message | Álvaro Herrera | 2025-02-21 18:46:06 | Re: Feature Request: multithreaded reindexdb --concurrently of a single table |