You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using asyncpg to query an postgres rds cluster. In my app I use asyncpg connection pools to aquire a connection and query the DB. I recently stood up an RDS Proxy in front of my RDS Cluster and I see almost 100% pinning because of the reset query used by asyncpg. I keep seeing the below message in my RDS Proxy logs for the pinned connections.
Consider moving session configuration to the proxy's initialization query. Digest: "select pg_advisory_unlock_all(); close all; unlisten *; reset all;".
Has anyone else run into connection pinning in RDS Proxy? I feel like the correct approach is not what is mentioned in the logs.
Thanks in advance :)
The text was updated successfully, but these errors were encountered:
I am using asyncpg to query an postgres rds cluster. In my app I use asyncpg connection pools to aquire a connection and query the DB. I recently stood up an RDS Proxy in front of my RDS Cluster and I see almost 100% pinning because of the reset query used by asyncpg. I keep seeing the below message in my RDS Proxy logs for the pinned connections.
Consider moving session configuration to the proxy's initialization query. Digest: "select pg_advisory_unlock_all(); close all; unlisten *; reset all;".
Has anyone else run into connection pinning in RDS Proxy? I feel like the correct approach is not what is mentioned in the logs.
Thanks in advance :)
The text was updated successfully, but these errors were encountered: