| From: | Neeta Ghadge <Neeta(dot)Ghadge(at)amdocs(dot)com> |
|---|---|
| To: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Guidance on avoiding session pinning with psqlODBC and RDS Proxy |
| Date: | 2025-11-16 14:53:02 |
| Message-ID: | GV2PR06MB1015502FA364CFD79E4F1412BFFC8A@GV2PR06MB10155.eurprd06.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hi,
We are currently using PostgreSQL 16.5 with the ODBC driver (psqlodbcw.so version 17.00.0006) in an environment that relies on Amazon RDS Proxy.
We have observed that the driver automatically issues the following SQL statements at connection startup:
SET DateStyle = 'ISO';
SET extra_float_digits = 2;
SHOW transaction_isolation;
While harmless in most cases, these queries cause AWS RDS Proxy to pin sessions, which reduces pooling efficiency. We can neutralize the SET commands using RDS Proxy's InitQuery feature, but SHOW transaction_isolation still forces pinning.
Could you please suggest recommended ways to handle this scenario when using psqlODBC with RDS Proxy? Specifically, are there configuration options or best practices to avoid or minimize session pinning while still maintaining ODBC compliance?
Thank you for your guidance.
Thanks and Regards,
Neeta Ghadge
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2025-11-17 16:21:45 | Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy |
| Previous Message | Dave Cramer | 2025-10-31 19:28:44 | Re: AIX 7.2 install psqlodbc with error |