AW: Reducing bandwidth usage of database replication - Mailing list pgsql-general
I have set the status interval to 600s and it still sends a status message every 30s.
I also tried setting every available option higher, with no success:
checkpoint_warning = 93s
max_standby_streaming_delay = 130s
max_standby_archive_delay = 45s
wal_receiver_status_interval = 600s
wal_receiver_timeout = 1200s
wal_receiver_timeout = 1200s
wal_receiver_timeout = 65s
recovery_min_apply_delay = 600s
The random values were to see which setting is limiting if I got above the 30s limit.
| ||
Gessler GmbH Gutenbergring 14 63110 Rodgau Deutschland |
Geschaeftsfuehrer: Helmut Gessler, Dipl.-Ing. Marcus Gessler
Gerichtsstand: Offenbach/Main, Amtsgericht Offenbach HRB 20857
USt.-IdNr.: DE 113 551 141
Sparkasse Dieburg, IBAN DE94 5085 2651 0057 0025 03, SWIFT HELADEF1DIE
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail
und/oder der Inhalte dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material of this e-mail is strictly forbidden.
Gerichtsstand: Offenbach/Main, Amtsgericht Offenbach HRB 20857
USt.-IdNr.: DE 113 551 141
Sparkasse Dieburg, IBAN DE94 5085 2651 0057 0025 03, SWIFT HELADEF1DIE
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail
und/oder der Inhalte dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material of this e-mail is strictly forbidden.
Von: Simon Riggs <simon.riggs@enterprisedb.com>
Gesendet: Freitag, 4. November 2022 10:16
An: Sascha Zenglein <zenglein@gessler.de>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Betreff: Re: Reducing bandwidth usage of database replication
Gesendet: Freitag, 4. November 2022 10:16
An: Sascha Zenglein <zenglein@gessler.de>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Betreff: Re: Reducing bandwidth usage of database replication
On Thu, 3 Nov 2022 at 08:40, Sascha Zenglein <zenglein@gessler.de> wrote:
It is, unfortunately, too much for our requirements.I was able to increase wal_receiver_status_interval so that the publisher only contacts the subscriber every 30 seconds instead of every 10.But I am not able to increase it further.
The max value is much higher than 30. Why can you not increase it further?
Attachment
pgsql-general by date: