Re: pg_dump on a standby for a very active master - Mailing list pgsql-general

From Stephen Frost
Subject Re: pg_dump on a standby for a very active master
Date
Msg-id 20190212175940.GQ6197@tamriel.snowman.net
Whole thread Raw
In response to Re: pg_dump on a standby for a very active master  (Arjun Ranade <ranade@nodalexchange.com>)
Responses Re: pg_dump on a standby for a very active master
List pgsql-general
Greetings,

* Arjun Ranade (ranade@nodalexchange.com) wrote:
> Yeah, that was one thing I was planning to try.  The other potential
> solution is to use barman (we are using barman on all db servers including
> standbys) to restore the latest backup to a VM and then take the pg_dump
> from there.  But I was hoping there would be a way in the settings to
> prevent such a workaround.

Performing a file-level backup and then restoring that and then
taking a pg_dump of restored cluster works quite well as a solution, in
my experience, even better is when you can do a delta restore over top
of the prior restore, updating just the files which were different, as
that can be much faster.

Thanks!

Stephen

Attachment

pgsql-general by date:

Previous
From: Scot Kreienkamp
Date:
Subject: RE: pg_dump on a standby for a very active master
Next
From: Arjun Ranade
Date:
Subject: Re: pg_dump on a standby for a very active master