On Thu, Nov 1, 2018 at 4:25 AM Jeff Janes wrote:
> On Wed, Oct 31, 2018 at 1:38 AM Torsten Förtsch
> wrote:
>> I am working on restoring a database from a base backup + WAL. With the
>> default settings the database replays about 3-4 WAL files per second. The
>> startup process takes about
This tool may be useful:
https://github.com/joyent/pg_prefaulter
Faults pages into PostgreSQL shared_buffers or filesystem caches in advance
of WAL apply
Nicolas
On Wed, Oct 31, 2018 at 6:38 AM Torsten Förtsch
wrote:
> Hi,
>
> I am working on restoring a database from a base backup + WAL.
Greetings,
* Jeff Janes (jeff.ja...@gmail.com) wrote:
> One way I found to speed up restore_command is to have another program run
> a few WAL files ahead of it, copying the WAL from the real archive into a
> scratch space which is on the same filesystem as pg_xlog/pg_wal. Then have
>
Greetings,
* Torsten Förtsch (tfoertsch...@gmail.com) wrote:
> I am working on restoring a database from a base backup + WAL. With the
> default settings the database replays about 3-4 WAL files per second. The
> startup process takes about 65% of a CPU and writes data with something
> between 50
On Wed, Oct 31, 2018 at 1:38 AM Torsten Förtsch
wrote:
> Hi,
>
> I am working on restoring a database from a base backup + WAL. With the
> default settings the database replays about 3-4 WAL files per second. The
> startup process takes about 65% of a CPU and writes data with something
> between
Hi,
I am working on restoring a database from a base backup + WAL. With the
default settings the database replays about 3-4 WAL files per second. The
startup process takes about 65% of a CPU and writes data with something
between 50 and 100 MB/sec.
Is there a way to speed that up? The disk can
