Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gtcLS-0004iR-UZ for pgsql-general@arkaria.postgresql.org; Tue, 12 Feb 2019 17:59:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gtcLR-0005rT-Fw for pgsql-general@arkaria.postgresql.org; Tue, 12 Feb 2019 17:59:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gtcLR-0005rL-7V for pgsql-general@lists.postgresql.org; Tue, 12 Feb 2019 17:59:45 +0000 Received: from tamriel.snowman.net ([96.255.250.162]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gtcLO-0001L9-Fb for pgsql-general@lists.postgresql.org; Tue, 12 Feb 2019 17:59:44 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 831585F79E; Tue, 12 Feb 2019 12:59:40 -0500 (EST) Date: Tue, 12 Feb 2019 12:59:40 -0500 From: Stephen Frost To: Arjun Ranade Cc: Scot Kreienkamp , "pgsql-general@lists.postgresql.org" Subject: Re: pg_dump on a standby for a very active master Message-ID: <20190212175940.GQ6197@tamriel.snowman.net> References: <17082AAFC33A934082836458CB53494374EB7F55@MONDB03.na.lzb.hq> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6eUvXotnMb6+obQB" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --6eUvXotnMb6+obQB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --6eUvXotnMb6+obQB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJcYwmMAAoJEO1sijiDR2RV79UQAKVkoDm8E8xwhwn2WMXVpcei RUQpKmmHxreO7foYy2NYM0rVDoC3Yl4NlLtvXneeCMkfFCDzE8YCGqsG+Yh99vYG 71HH5SLZ61tKyZAoU+pj5wQPUQdqURy7fdgJhMiC132DgBWn6Ii63NZHQ6tsFtY8 Ai6bRlbhdVSghYBYGUOdDSrBBj9zTlUqHF7FZalDXjBgdsg/2EvpPPIWQP9Ahzde w8Og4L0uCcXVtcl8zMxjYqO0ri9cpYGGVZkECRrSK5CtszgtEdTB5MXWSRZDvZfX fI6P/ujXhw3jAFYD7ZpH8BAPtF0JaxWpJrNPKio2Q/iw5+rDbwTjD+xgNryIuzEU 8Koyy35WY1l+eDr7Q/NMjp4HE4EkDMZ/yjbatg4sP8V77y5F1kZwq2+OuuVSCv5H OWNKtK0T83bhCuOj/0eQ+WvHz3Xkh7CHPQJAYbLuyCr+bD/y7Q3n75YqaOdXmu6h wBFmBVUriGBxZtwS/obR0mjUOE1Nl9/HnjMmNPT0nEI5KqiSK2FX0UiGehj1T0oz dNf46cEgCdykrKnJ5gnk3Sq8mNChGoeiGy0RYaxOtl+ATcOa+7ThaBipyb2ZOaMn vKj2lX5Sc5Wp1yahaKdY4u1+OTo1T2GcgjDI3sfcQUqMA5ZMd3EZissOrEO4Vh82 bmIjHKsmEpDX+nWkc42n =6zm3 -----END PGP SIGNATURE----- --6eUvXotnMb6+obQB--