Setting up continuous archiving

2018-09-26 Thread Yuri Kanivetsky
ve are 0600, ~/base_backups/TIMESTAMP is 0700. How can I confirm that it's working properly? Is WAL segments files appearing in ~/wal_archive enough? Thanks in advance. Regards, Yuri Kanivetsky

Re: Setting up continuous archiving

2018-10-15 Thread Yuri Kanivetsky
eks period. Is that doable with both of them (pgBackRest, Barman)? Does it make sense to use repmgr with pgBackRest? Regards, Yuri Kanivetsky On Wed, Sep 26, 2018 at 8:19 PM Pierre Timmermans wrote: > > Hello > > What you are doing is called "log shipping", which means that when a wa

Re: Setting up continuous archiving

2018-10-15 Thread Yuri Kanivetsky
ssible. Ideally, automatically. Which probably means either repmgr, or corosync + pacemaker + PAF. Is that what you mean by HA here? Or at least, have a running instance I can switch to manually. Which means, for example, pgBackRest's streaming replication. Regards, Yuri Kanivetsky

New timeline when starting with a restored data dir

2018-11-18 Thread Yuri Kanivetsky
Hi, I'm trying to set up Barman, and I've noticed that PostgreSQL 10 creates a new timeline when starting with a restored data dir. Particularly, when WAL files are delivered via restore_command. When WAL files are copied to pg_wal dir, no new timeline is created. Is it to be expected? Can you exp