| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: parallelizing the archiver |
| Date: | 2021-09-10 18:34:00 |
| Message-ID: | 30EBF35A-C1A3-426E-A37E-6A56206E9CE4@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 10 сент. 2021 г., в 22:18, Bossart, Nathan <bossartn(at)amazon(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-09-10 19:44:22 | Re: extensible options syntax for replication parser? |
| Previous Message | Jaime Casanova | 2021-09-10 18:30:23 | Re: WIP: System Versioned Temporal Table |