Hi Basti,
When you are dumping a big table using hot_standby_feedback=on,you are holding
the master from cleaning up old records(as in: it was running on master).
If too much time elapses while the lock is held (30 secs by default), then the
statementis cancelled.
At the expense of potentiall
Thanks a lot for this tip. I don't know is this is the right param.
Becouse of: "... , but can cause database bloat on the primary for some
workloads."
This the an other way to backup the database and work around
pg_dump: Error message from server: ERROR: canceling statement due to
conflict wit
On 24 July 2018 14:44:45 CEST, basti wrote:
>Hello,
>
>we have a db master and a slave.
-
>
>How can I do an backup with pg_dumpall from slave?
Set hot_standby_feedback to on.
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company
Hello,
we have a db master and a slave.
master conf:
wal_level = replica
max_wal_senders = 5
wal_keep_segments = 100
archive_mode = on
archive_command = 'rsync -a %p -e "ssh -i
/var/lib/postgresql/.ssh/id_rsa"
postgres@slave:/var/lib/postgresql/9.6/wals/master/%f https://www.postgresql.org/me
