# Improve RDS Proxy multiplexing for PostgreSQL, Part 1: Common causes

DevFeed: [Improve RDS Proxy multiplexing for PostgreSQL, Part 1: Common causes](<https://devfeed.tech/articles/improve-rds-proxy-multiplexing-for-postgresql-part-1-common-causes-133437.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/improve-rds-proxy-multiplexing-for-postgresql-part-1-common-causes/>)

Author: Pavel Rabinovich

Published: 2026-11-13T21:08:09Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [fragmentation](<https://devfeed.tech/tags/fragmentation.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [pool](<https://devfeed.tech/tags/pool.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

## AI overview

RDS Proxy multiplexing for PostgreSQL is reduced when sessions are pinned, client identities fragment the pool, or transactions remain open. CloudWatch indicators help distinguish them: elevated session-pinned connections suggest pinning; many backend connections with low borrowing and pinning can indicate fragmentation; sustained borrowing and open transactions point to transactions held too long. Fixes include upgrading the PostgreSQL JDBC driver to 42.7.x or newer, removing application SET statements, setting Spark JDBC writes to isolationLevel=NONE, and using InitQuery for shared session defaults. Standardize username, database, and ApplicationName among clients that should share a pool, while preserving separate users when privilege or audit needs require them. Commit promptly or enable autocommit where explicit transaction control is unnecessary. PostgreSQL targets do not support the proxy's SET pinning filter, and CloudWatch gauges can miss short-lived borrow cycles.

## Source excerpt

RDS Proxy multiplexes many client connections across a small pool of database connections, but connection pinning, pool fragmentation, and uncommitted transactions can silently disable that benefit for PostgreSQL workloads. Part 1 shows how to recognize each condition with Amazon CloudWatch metrics and the fix that restores multiplexing.