Hello Stephen,
> On 19 Oct 2020, at 23:25, Stephen Frost wrote:
>
> Greetings,
>
Implementation of this approach assumes running several background
processes (bgworkers)
each of which runs a shell command specified by the parameter
restore_command
to deliver an archiv
Hi StephenBased on our last discussion I redesigned the implementation of WAL archive recovery speed-up. The main idea of the new implementation was partly borrowed from your proposal, to be more accurate from the following one:On 9 Nov 2020, at 23:31, Stephen Frost wrote:The r
Hello hackers,
Currently, database recovery from archive is performed sequentially,
by reading archived WAL files and applying their records to the database.
Overall archive file processing is done one by one, and this might
create a performance bottleneck if archived WAL files are delivered slow
Hello Stephen
> On 9 Sep 2020, at 21:26, Stephen Frost wrote:
>
> Greetings,
>
> * Dmitry Shulga (d.shu...@postgrespro.ru) wrote:
>> Overall archive file processing is done one by one, and this might
>> create a performance bottleneck if archived WAL files are deliv