Implement dynamic scaling for Postgres Max Connections based on memory
Follow up from !6574 (comment 1231776625)
Postgres max connections requirements can vary depending on the size of the environment and expected user count. Testing against our 50k Reference Architecture found it needed over 300 connections but the previous default was 200. After discussion the limit is increased now to 400 but the trade off here is each connection consumes memory so this limit may have an impact on smaller setups.
The right solution then arguably is to have a dynamic setting by default where it scales the connections based on memory. Request is for this to be implemented as a graceful solution.