pg_dump from a hot standby replication slave

From: Johan Thomsen <johan(at)cellpointmobile(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: pg_dump from a hot standby replication slave
Date: 2016-06-20 14:22:19
Message-ID: CABxB1bu03fbXJtO1BkRqGugxZ-dzqhabcE1AFOROth8zWPZrTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

In relation to this thread:
https://www.postgresql.org/message-id/0B4197B9-5DB8-4475-A83C-38DA5965782A%40etasseo.com

> I ran the pg_dump process again this morning, ensuring that the standby
> parameters were set, and it completed successfully with the
> hot_standby_feedback enabled.

In case I were to set the hot_standby_feedback param to "on" at my
slave node for the _only_ reason that I would like to make a dump of a
database while replication is running, how would it affect the primary
node performance-wise?

Worth mentioning: I do not require the dumped data to be highly
up-to-date, I just need a static snapshot, knowing perfectly well that
data is updated continuously while dumping.

Are there perhaps other ways to perform a dump of a hot standby node
without affecting the primary node performance and without stopping or
pausing the replication?
Version: postgres (PostgreSQL) 9.2.2

Thank you in advance,

Regards,
Johan

--
Johan Thomsen

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martín Marqués 2016-06-20 14:23:15 Re: R: Vacuum full: alternatives?
Previous Message Greg Navis 2016-06-20 14:04:31 Re: [pg_trgm] Making similarity(?, ?) < ? use an index