AW: Reducing bandwidth usage of database replication

[Sascha Zenglein <zenglein@xxxxxxxxxx>]

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.

Sascha Zenglein Produktentwicklung

 

---

Gessler GmbH Gutenbergring 14 63110 Rodgau Deutschland

Tel.:  +49 6106 8709 693 Fax:  +49 6106 8709 50   E-Mail: zenglein@xxxxxxxxxx Web: www.gessler.de

---

 

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.

---

Von: Ron <ronljohnsonjr@xxxxxxxxx>
Gesendet: Mittwoch, 2. November 2022 17:29
An: pgsql-general@xxxxxxxxxxxxxxxxxxxx <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
Betreff: Re: Reducing bandwidth usage of database replication

 

On 11/2/22 09:56, Sascha Zenglein wrote:

Hi all,

I want to use the postgres-native logical replication to have multiple clients receive and send data to a central database.

Real-time is far less important than network usage, and with my current test setup it appears both instances communicate frequently if a subscription is active, even if nothing is happening.

Is there a good way to reduce data usage, for example by limiting the amount of keep-alive messages? One database will likely be idle most of the time.

I estimated the current solution to idle at around 1.4MiB per day. Ideally it would use less than 100KiB a day.

1.4MiB/day is 17 bytes per second.  That's not too much.

--
Angular momentum makes the world go 'round.