| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Zahir Lalani <ZahirLalani(at)oliver(dot)agency> |
| Cc: | Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Multi-master replication |
| Date: | 2021-08-13 12:18:20 |
| Message-ID: | 20210813121820.GD4822@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Aug 13, 2021 at 11:35:29AM +0000, Zahir Lalani wrote:
> Confidential
>
> Thx Laura
>
> So here is the dilemma - everything in the cloud world tends toward horizontal scaling. We do that with PG using single master and multiple slaves. But we are write heavy and of course the load on the master is quite high. It does seem that multi-master has risks (everyone seems to talk about conflict resolution!) so I wonder whether the sensible route is simply to scale vertically on the master?
>
> We are looking at pg_pool II to manage the current config - which I suppose will help with the connection pooling etc. But even it lends caution to the multi-master route for write heavy applications.
You might want to read this:
https://momjian.us/main/blogs/pgblog/2018.html#December_24_2018
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vijaykumar Jain | 2021-08-13 12:19:48 | Re: Multi-master replication |
| Previous Message | Zahir Lalani | 2021-08-13 11:35:29 | RE: Multi-master replication |