Re: parallelizing the archiver - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: parallelizing the archiver
Date
Msg-id 30EBF35A-C1A3-426E-A37E-6A56206E9CE4@yandex-team.ru
Whole thread Raw
In response to Re: parallelizing the archiver  ("Bossart, Nathan" <bossartn@amazon.com>)
Responses Re: parallelizing the archiver  ("Bossart, Nathan" <bossartn@amazon.com>)
Re: parallelizing the archiver  ("Bossart, Nathan" <bossartn@amazon.com>)
List pgsql-hackers

> 10 сент. 2021 г., в 22:18, Bossart, Nathan <bossartn@amazon.com> написал(а):
>
> I was thinking that archive_batch_size would be the maximum batch
> size.  If the archiver only finds a single file to archive, that's all
> it'd send to the archive command.  If it finds more, it'd send up to
> archive_batch_size to the command.

I think that a concept of a "batch" is misleading.
If you pass filenames via stdin you don't need to know all names upfront.
Just send more names to the pipe if achiver_command is still running one more segments just became available.
This way level of parallelism will adapt to the workload.

Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: WIP: System Versioned Temporal Table
Next
From: Robert Haas
Date:
Subject: Re: extensible options syntax for replication parser?