Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy

Hi Neeta,

I'm curious why RDSProxy is pinning on this. I can't think of any reason to
pin on a SHOW
That said, I'm equally curious why psqlODBC is doing it, it doesn't really
need to know the transaction isolation level

Dave Cramer
www.postgres.rocks

On Mon, 17 Nov 2025 at 05:19, Neeta Ghadge <Neeta(dot)Ghadge(at)amdocs(dot)com> wrote:

> 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*
>
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may review at
> https://www.amdocs.com/about/email-disclaimer
>
> Amdocs Development Centre India Private Limited having CIN:
> U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP
> (A limited liability partner­ship with LLP Identification Number:
> AAI-6901 effective 28th Feb 2017)
>