%3CLINGO-SUB%20id%3D%22lingo-sub-1757266%22%20slang%3D%22en-US%22%3EAnalyzing%20the%20Limits%20of%20Connection%20Scalability%20in%20Postgres%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1757266%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20common%20challenge%20with%20Postgres%20for%20those%20of%20you%20who%20manage%20busy%20Postgres%20databases%2C%20and%20those%20of%20you%20who。%20foresee%20being%20in%20that%20situation%2C%20is%20that%20Postgres%20does%20not%20handle%20large%20numbers%20of%20connections%20particularly%20well.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3EWhile%20it%20is%20possible%20to%20have%20a%20few%20thousand%20established%20connections%20without%20running%20into%20problems%2C%20there%20are%20some%20real%20and%20hard-to-avoid%20problems.%3C%2FP%3E。%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESince%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-database-for-postgresql%2Fmicrosoft-azure-welcomes-postgresql-committers%2Fba-p%2F1207612%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ejoining%20Microsoft%3C%2FA%3E%20last%20year%20in%20the%20%3CA%20href%3D%22https%3A%2F。%2Fazure.microsoft.com%2Fservices%2Fpostgresql%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Database%20for%20PostgreSQL%3C%2FA%3E%20team%E2%80%94where%20I%20work%20on%20open%20source%20Postgres%E2%80%94I%20have%20spent%20a%20lot%20of%20time%20analyzing%20and%20addressing%20some%20of%20the%20issues%20with%20connection%20scalability%20in%20Postgres.%3C%。2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20this%20post%20I%20will%20explain%20why%20I%20think%20it%20is%20important%20to%20improve%20Postgres'；%20handling%20of%20large%20number%20of%20connections.%20Followed%20by%20an%20analysis%20of%20the%20different%20limiting%20aspects%20to%20connection%20scalability%20in%20Postgres.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20an%20upcoming%20post%20I%20will%20show%20the%20results%20of%20the%20work%20we%E2%80%99ve%20done%20to%20improve%20connection%20handling%20and%20snapshot%20scalability%20in%20Postgres。%E2%80%94and%20go%20into%20detail%20about%20the%20identified%20issues%20and%20how%20we%20have%20addressed%20them%20in%20Postgres%2014.%3C%2FP%3E%0A%3CHR%20%2F%3E%0A%3CDIV%20class%3D%22toc%22%3E%3CNAV%20id%3D%22TableOfContents%22%3E%0A%3COL%3E%0A%3CLI%3E%3CA%20href%3D%22%23why-connection-scalability-in-postgres-is-important%22%20target%。3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EWhy%20connection%20scalability%20in%20Postgres%20is%20important%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22%23surveying-connection-scalability-issues%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESurveying%20connection%20scalability%20issues%3C%2FA%3E%3C%2FLI%3E%。0A%3CLI%3E%3CA%20href%3D%22%23memory-usage%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMemory%20usage%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22%23constant-connection-overhead%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EConstant%20connection%20overhead%3C%2FA%。3E%3COL%3E%0A%3CLI%3E%3CA%20href%3D%22%23conclusion-connection-memory-overhead-is-acceptable%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EConclusion%3A%20connection%20memory%20overhead%20is%20acceptable%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22%23cache-bloat%。22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECache%20bloat%3C%2FA%3E%3COL%3E%0A%3CLI%3E%3CA%20href%3D%22%23problem-illustration%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EProblem%20illustration%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22%23conclusion-。Cache-bloat-is-not-the-major-issue-at-this-moment%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EConclusion%3A%20cache%20bloat%20is%20not%20the%20major%20issue%20at%20this%20moment%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22%23query-memory-usage%。22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EQuery%20memory%20usage%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22%23snapshot-scalability%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESnapshot%20scalability%3C%2FA%3E%3COL%3E%0A%3CLI%3E%3CA%20href%3D%22%。23cause%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECause%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22%23conclusion-snapshot-scalability-is-a-significant-limit%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EConclusion%3A%20Snapshot%20scalability%20