Well...
In my personal experience, I have a multi GB customer database. During the PG dump, when the source (master) database is modified, my pg_dump fails.
Pausing replication resolves that problem. From: pgsql-admin-owner@xxxxxxxxxxxxxx <pgsql-admin-owner@xxxxxxxxxxxxxx> on behalf of Suresh Rajagopal <sureshr7@xxxxxxxxx>
Sent: Thursday, February 2, 2017 12:59 PM To: John Scalia Cc: Pgsql-admin Subject: Re: How to stop Streaming Replication in slave for backup Thanks John.
From: John Scalia <jayknowsunix@xxxxxxxxx> To: Suresh Rajagopal <sureshr7@xxxxxxxxx> Cc: Pgsql-admin <pgsql-admin@xxxxxxxxxxxxxx> Sent: Thursday, February 2, 2017 10:27 AM Subject: Re: How to stop Streaming Replication in slave for backup You really shouldn't need to stop replication in order to run pg_dump on a 9.3 database,
On Thu, Feb 2, 2017 at 1:07 PM, Suresh Rajagopal <sureshr7@xxxxxxxxx> wrote:
Journyx, Inc.
7600 Burnet Road #300
Austin, TX 78757 www.journyx.com p 512.834.8888
f 512-834-8858
Do you receive our promotional emails? You can subscribe or unsubscribe to those emails at http://go.journyx.com/emailPreference/e/4932/714/
|