Re: Reduce the time required for a database recovery from archive.

From: David Steele <david(at)pgmasters(dot)net>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Dmitry Shulga <d(dot)shulga(at)postgrespro(dot)ru>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Reduce the time required for a database recovery from archive.
Date: 2021-03-18 15:46:38
Message-ID: d7391d83-dbca-6680-b51b-f2af99458cde@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/18/21 11:37 AM, Andrey Borodin wrote:
>
>
>> 18 марта 2021 г., в 20:04, David Steele <david(at)pgmasters(dot)net> написал(а):
>> it would be nice to support an interface that simply says to the restore_command, "go get 1gb of WAL and write the files here."
>
> +1 to redesigning restore_command and archive_command.

Indeed, archive_command would benefit from the same treatment. The need
to call archive_command for each WAL segment even when parallel
processing is going on behind the scenes is a bottleneck.

Larger WAL segments sizes can be used to mitigate this issue but an
improvement would be welcome.

Regards,
--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2021-03-18 15:50:02 Re: pg_stat_statements and "IN" conditions
Previous Message Andrey Borodin 2021-03-18 15:37:57 Re: Reduce the time required for a database recovery from archive.