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 with recovery # DETAIL: User was holding a relation lock for too long. this error? I have try bg_asepackup but this close with: pg_basebackup: could not connect to server: FATAL: number of requested standby connections exceeds max_wal_senders (currently 0) Best regards, On 24.07.2018 15:33, Andreas Kretschmer wrote: > On 24 July 2018 14:44:45 CEST, basti <mailinglist@xxxxxxxxxxxxxxxx> 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 > >
