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. Z > -----Original Message----- > From: Laura Smith <n5d9xq3ti233xiyif2vp@xxxxxxxxxxxxx> > Sent: 13 August 2021 10:47 > To: Zahir Lalani <ZahirLalani@oliver.agency> > Cc: pgsql-general@xxxxxxxxxxxxxxxxxxxx > Subject: Re: Multi-master replication > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On Friday, August 13th, 2021 at 9:00 AM, Zahir Lalani > <ZahirLalani@oliver.agency> wrote: > > > Confidential > > > > Hello all > > > > Does anyone on the list have production experience of using PG in a multi- > master setup – if so using which tools? > > > > Thx > > > > Zahir > > > > I have sometimes considered it, but it always struck me that given there is no > first-class support for it, multi-master in postgres is just an opportunity for so > many foot-guns to enable to things to go terribly, terribly wrong. > > Maybe you need to look at something like CockroachDB which has a degree of > Postgres syntax compatability (https://www.cockroachlabs.com/blog/why- > postgres/). N.B. Not speaking from experience here, CockroachDB is > something I've wanted to play with for a long time but never had the time ! >
