Horton
Menu

Re: Add Index-level REINDEX with multiple jobs

Svetlana Derevyanko <s.derevyanko@postgrespro.ru>

View thread
From: Svetlana Derevyanko <s.derevyanko@postgrespro.ru>
To: "Andrey M. Borodin" <x4mmm@yandex-team.ru>
Cc: Michael Paquier <michael@paquier.xyz>, Maxim Orlov <orlovmg@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-03-11T08:38:40Z
Lists: pgsql-hackers

Attachments

Andrey M. Borodin писал(а) 2024-03-04 09:26:
>> On 6 Feb 2024, at 11:21, Michael Paquier <michael@paquier.xyz> wrote:
>> 
>> The problem may be actually trickier than that, no?  Could there be
>> other factors to take into account for their classification, like
>> their sizes (typically, we'd want to process the biggest one first, I
>> guess)?
> 
> Maxim, what do you think about it?
> 
> 
> Best regards, Andrey Borodin.

I agree that, as is the case with tables in REINDEX SCHEME, indices 
should be sorted accordingly to their size.

Attaching the second version of patch, with indices being sorted by 
size.

Best regards,
Svetlana Derevyanko

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. reindexdb: Fix warning about uninitialized indices_tables_cell

  2. reindexdb: Add the index-level REINDEX with multiple jobs