| From: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Feature Request: multithreaded reindexdb --concurrently of a single table |
| Date: | 2025-02-21 18:46:06 |
| Message-ID: | 202502211846.grjzhouis773@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Ed is the standard text editor."
http://groups.google.com/group/alt.religion.emacs/msg/8d94ddab6a9b0ad3
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2025-02-22 00:03:06 | Re: Feature Request: multithreaded reindexdb --concurrently of a single table |
| Previous Message | Laurenz Albe | 2025-02-21 07:01:02 | Re: May data be corrupted after an interrupted, but afterwards sucessfully replayed recovery? |