Postgres replica count limits?

I am consider using postgres for a highly replicated KV store that will push down changes to a high number of regions. Sort of like Cloudflare KV but pushing updates down to the cached regions rather than waiting for the first request and getting at least one very slow response.

Are there any limits in terms of number of replicas that I should be considering for this? For example if I made a primary instance with 8vCPU and then had a 4vCPU replica in EVERY available region, what problems start to arise?

This is like 99.999999% read operations so the optimization is for lowering read latency around the world, without waiting for a request to cache a value locally.

@danthegoodman The default configuration supports up to 10 replicas. This isn’t a restriction, however, and this limit can be bumped by adjusting the max_wal_senders and max_replication_slot Postgres configuration values.

Thanks @shaun , have there been any tests done at say 26 replicas?

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.