| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Reducing bandwidth usage of database replication |
| Date: | 2022-11-02 16:29:47 |
| Message-ID: | f3b7d9b9-a620-11d2-ffdc-e07b4b9821c1@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryn Llewellyn | 2022-11-02 22:31:22 | Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all" |
| Previous Message | Sascha Zenglein | 2022-11-02 14:56:22 | Reducing bandwidth usage of database replication |