From: | Yaser Raja <yrraja(at)gmail(dot)com> |
---|---|
To: | Ajlinux <ajlinux(at)protonmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Repmgr and pg_dump conflict when backing up from standby |
Date: | 2017-04-28 22:44:06 |
Message-ID: | CALkbEVnLJ+OE3-mOsags02F3RUVaLxUka9kcL_SnftbPS0bc=g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Check out the configuration parameter "hot_standby_feedback"
Setting this parameter to 'on' will eliminate the query cancellation caused
by the vacuum related conflicts.
Check out the documentation for more details:
https://www.postgresql.org/docs/9.4/static/runtime-
config-replication.html
Also check out the parameters max_standby_streaming_delay and
max_standby_archive_delay.
Regards
Yaser
On Fri, Apr 28, 2017 at 8:09 AM, Ajlinux <ajlinux(at)protonmail(dot)com> wrote:
> Hi
>
> I am doing replication using repmgr from master to standby. I am trying
> to do my pg_dump of a database from the standby and the pg_dump always
> fails with:
>
> Cancelling statement due to conflict with recovery.
>
> Is there anything special you need to do to get pg_dump working on the
> standby. Please advise the best way to do this.
>
> I am running Postgres 9.4 on Ubuntu 14.04.
>
> Sent from ProtonMail <https://protonmail.com>, Swiss-based encrypted
> email.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rahul Sharma | 2017-05-01 19:32:04 | San replication corrupting postgres file... |
Previous Message | Ajlinux | 2017-04-28 12:09:57 | Repmgr and pg_dump conflict when backing up from standby |