Re: parallelizing the archiver

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: parallelizing the archiver
Date: 2021-09-09 22:30:54
Message-ID: BE033CAA-6541-4565-AF5D-4FA18F7EFF68@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/7/21, 11:38 PM, "Julien Rouhaud" <rjuju123(at)gmail(dot)com> wrote:
> On Wed, Sep 8, 2021 at 6:36 AM Bossart, Nathan <bossartn(at)amazon(dot)com> wrote:
>>
>> I'd like to gauge interest in parallelizing the archiver process.
>> [...]
>> Based on previous threads I've seen, I believe many in the community
>> would like to replace archive_command entirely, but what I'm proposing
>> here would build on the existing tools.
>
> Having a new implementation that would remove the archive_command is
> probably a better long term solution, but I don't know of anyone
> working on that and it's probably gonna take some time. Right now we
> have a lot of users that face archiving bottleneck so I think it would
> be a good thing to implement parallel archiving, fully compatible with
> current archive_command, as a short term solution.

Thanks for chiming in. I'm planning to work on a patch next week.

Nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bossart, Nathan 2021-09-09 22:49:46 Re: pg_walinspect - a new extension to get raw WAL data and WAL stats
Previous Message Bossart, Nathan 2021-09-09 22:24:30 Re: .ready and .done files considered harmful