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

public inbox for pgsql-odbc@postgresql.org  
help / color / mirror / Atom feed

From: Dave Cramer <davecramer@postgres.rocks>
To: Neeta Ghadge <Neeta.Ghadge@amdocs.com>
Cc: pgsql-odbc@postgresql.org <pgsql-odbc@postgresql.org>
Subject: Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy
Date: Mon, 17 Nov 2025 11:21:45 -0500
Message-ID: <CADK3HH+rYX2vnej0gPy7Z5V7+McsygDaBsdhUmQVPXjwPTuZqA@mail.gmail.com> (raw)
In-Reply-To: <GV2PR06MB1015502FA364CFD79E4F1412BFFC8A@GV2PR06MB10155.eurprd06.prod.outlook.com>
References: <GV2PR06MB1015502FA364CFD79E4F1412BFFC8A@GV2PR06MB10155.eurprd06.prod.outlook.com>

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.Ghadge@amdocs.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 partnership with LLP Identification Number:
> AAI-6901 effective 28th Feb 2017)
>

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-odbc@postgresql.org
  Cc: davecramer@postgres.rocks, Neeta.Ghadge@amdocs.com
  Subject: Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy
  In-Reply-To: <CADK3HH+rYX2vnej0gPy7Z5V7+McsygDaBsdhUmQVPXjwPTuZqA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox