From: Stephen Frost <sfrost@snowman.net>
To: For@ll <forall@stalowka.info>
Cc: pgsql-admin@postgresql.org
Subject: Re: Pgbackrest
Date: Fri, 12 Oct 2018 08:07:38 -0400
Message-ID: <20181012120738.GQ4184@tamriel.snowman.net> (raw)
In-Reply-To: <ppph0a$l1r$1@blaine.gmane.org>
References: <ppph0a$l1r$1@blaine.gmane.org>
Greetings,
* For@ll (forall@stalowka.info) wrote:
> For now I use OmniPITR for backup and replication with postgresql, but
> we looking something else and I find pgbackrest, so I have a few questions:
>
> - use OmniPITR for streaming replication I have 2 way protection, when
> slave long time off,after start, postgresql restore data from wal before
> switching to the streamgin replication from postgresql.
> It's possible to do in pgbackrest?
Yes, when you do a restore with pgbackrest, the recovery.conf will be
set up to pull WAL from the repository to catch up.
> - in pgbackrest streaming replication it can be only with "async state"?
Note that pgbackrest doesn't use streaming replication for WAL as it's
too slow, we use archive_command instead (and will run multiple parallel
workers to get ahead of where archive_command is at, if there's WAL
available to process and parallel workers are configured).
It doesn't matter to pgbackrest if the replication between your primary
and replica is synchronous or asycnhronous.
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: sfrost@snowman.net, forall@stalowka.info
Subject: Re: Pgbackrest
In-Reply-To: <20181012120738.GQ4184@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox