Re: pgsql: reindexdb: Add the index-level REINDEX with multiple jobs
От | Alexander Korotkov |
---|---|
Тема | Re: pgsql: reindexdb: Add the index-level REINDEX with multiple jobs |
Дата | |
Msg-id | CAPpHfdteHycyc2WjXx06kseek3YO_Yaii158i3wOkwm82=HMyg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgsql: reindexdb: Add the index-level REINDEX with multiple jobs (Álvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: pgsql: reindexdb: Add the index-level REINDEX with multiple jobs
|
Список | pgsql-hackers |
On Fri, Mar 7, 2025 at 8:20 PM Álvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > On 2024-Mar-25, Alexander Korotkov wrote: > > > reindexdb: Add the index-level REINDEX with multiple jobs > > > > Straight-forward index-level REINDEX is not supported with multiple jobs as > > we cannot control the concurrent processing of multiple indexes depending on > > the same relation. Instead, we dedicate the whole table to certain reindex > > job. Thus, if indexes in the lists belong to different tables, that gives us > > a fair level of parallelism. > > I tested this, because of a refactoring suggestion [1] and I find that > it's rather completely broken. The code was written with assumption that running run_reindex_command() with async == true can schedule a number of queries for a connection. But actually that's not true and everything is broken. ------ Regards, Alexander Korotkov Supabase
В списке pgsql-hackers по дате отправления: