Re: Progress report of CREATE INDEX for nested partitioned tables
От | Matthias van de Meent |
---|---|
Тема | Re: Progress report of CREATE INDEX for nested partitioned tables |
Дата | |
Msg-id | CAEze2Wgj=Ktn_B4U1sRRnWwitQcB4gLkb1QR8627bGRfzW4QOA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Progress report of CREATE INDEX for nested partitioned tables (Ilya Gladyshev <ilya.v.gladyshev@gmail.com>) |
Ответы |
Re: Progress report of CREATE INDEX for nested partitioned tables
|
Список | pgsql-hackers |
On Wed, 1 Feb 2023 at 18:51, Ilya Gladyshev <ilya.v.gladyshev@gmail.com> wrote: > > 1 февр. 2023 г., в 20:27, Matthias van de Meent <boekewurm+postgres@gmail.com> написал(а): > >> In HEAD we set TOTAL to whatever number partitioned table we're >> currently processing has - regardless of whether we're the top level >> statement. >> With the patch we instead add the number of child relations to that >> count, for which REL_HAS_STORAGE(child) -- or at least, in the v3 >> posted by Ilya. Approximately immediately after updating that count we >> recurse to the child relations, and that only returns once it is done >> creating the indexes, so both TOTAL and DONE go up as we process more >> partitions in the hierarchy. > > > The TOTAL in the patch is set only when processing the top-level parent and it is not updated when we recurse, so yes,it is constant. From v3: Ugh, I misread the patch, more specifically count_leaf_partitions and the !OidIsValid(parentIndexId) condition changes. You are correct, sorry for the noise. Kind regards, Matthias van de Meent
В списке pgsql-hackers по дате отправления: