Re: Making WAL archiving faster — multi-file support and async ideas - Mailing list pgsql-hackers

From Alyona Vinter
Subject Re: Making WAL archiving faster — multi-file support and async ideas
Date
Msg-id CAGWv16KXBCvNXBbe+MbNtFQMKfbhOfhJMdGajdiKwxUPWyateg@mail.gmail.com
Whole thread Raw
In response to Re: Making WAL archiving faster — multi-file support and async ideas  (Greg Sabino Mullane <htamfids@gmail.com>)
List pgsql-hackers
Hi Greg!

Thanks for your question — it made me take a closer look at the recovery process. You're absolutely right, and I appreciate you pointing that out.
Postgres requests history files from the archive, which helps determine whether to wait for the next segment or if the timeline is finished. If Postgres detects that the segment isn't in the archive yet, it simply waits for it to appear. Let me know if I’ve missed anything here.
Then I see no fundamental problem with the parallel archiver =)

Best wishes,
Alyona Vinter

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Calling PGReserveSemaphores() from CreateOrAttachShmemStructs
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: Explicitly enable meson features in CI