public inbox for [email protected]help / color / mirror / Atom feed
Guidance on avoiding session pinning with psqlODBC and RDS Proxy 8+ messages / 3 participants [nested] [flat]
* Guidance on avoiding session pinning with psqlODBC and RDS Proxy @ 2025-11-16 14:53 Neeta Ghadge <[email protected]> 2025-11-17 16:21 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 0 siblings, 1 reply; 8+ messages in thread From: Neeta Ghadge @ 2025-11-16 14:53 UTC (permalink / raw) To: 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 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 <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) ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy 2025-11-16 14:53 Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> @ 2025-11-17 16:21 ` Dave Cramer <[email protected]> 2025-11-17 16:44 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 0 siblings, 1 reply; 8+ messages in thread From: Dave Cramer @ 2025-11-17 16:21 UTC (permalink / raw) To: Neeta Ghadge <[email protected]>; +Cc: pgsql-odbc 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 <[email protected]> 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) > ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy 2025-11-16 14:53 Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 16:21 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> @ 2025-11-17 16:44 ` Dave Cramer <[email protected]> 2025-11-17 16:52 ` RE: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 0 siblings, 1 reply; 8+ messages in thread From: Dave Cramer @ 2025-11-17 16:44 UTC (permalink / raw) To: Neeta Ghadge <[email protected]>; +Cc: pgsql-odbc Hi, Neeta, Talking to some folks at Amazon, they don't think it should pin. Can you open a ticket with them? Dave Cramer www.postgres.rocks On Mon, 17 Nov 2025 at 11:21, Dave Cramer <[email protected]> wrote: > 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 <[email protected]> > 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) >> > ^ permalink raw reply [nested|flat] 8+ messages in thread
* RE: Guidance on avoiding session pinning with psqlODBC and RDS Proxy 2025-11-16 14:53 Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 16:21 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 2025-11-17 16:44 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> @ 2025-11-17 16:52 ` Neeta Ghadge <[email protected]> 2025-11-17 17:01 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 0 siblings, 1 reply; 8+ messages in thread From: Neeta Ghadge @ 2025-11-17 16:52 UTC (permalink / raw) To: Dave Cramer <[email protected]>; +Cc: pgsql-odbc Hi, Thank you for your prompt response. It's not SHOW command, rather it is SET that is causing session pinning. I will try to find alternate approaches to avoid session pinning. Thanks and Regards, Neeta Ghadge From: Dave Cramer <[email protected]> Sent: Monday, November 17, 2025 10:14 PM To: Neeta Ghadge <[email protected]> Cc: [email protected] Subject: Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification; CAUTION: This email is from an external source. Please don't open any unknown links or attachments. Hi, Neeta, Talking to some folks at Amazon, they don't think it should pin. Can you open a ticket with them? Dave Cramer www.postgres.rocks<http://www.postgres.rocks; On Mon, 17 Nov 2025 at 11:21, Dave Cramer <[email protected]<mailto:[email protected]>> wrote: 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<http://www.postgres.rocks; On Mon, 17 Nov 2025 at 05:19, Neeta Ghadge <[email protected]<mailto:[email protected]>> 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) 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 <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) ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy 2025-11-16 14:53 Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 16:21 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 2025-11-17 16:44 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 2025-11-17 16:52 ` RE: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> @ 2025-11-17 17:01 ` Dave Cramer <[email protected]> 2025-11-17 17:12 ` RE: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 17:23 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Jon Raiford <[email protected]> 0 siblings, 2 replies; 8+ messages in thread From: Dave Cramer @ 2025-11-17 17:01 UTC (permalink / raw) To: Neeta Ghadge <[email protected]>; +Cc: pgsql-odbc Ah, OK, I will have to change the driver. I think that is doable. Can you create an issue here https://github.com/postgresql-interfaces/psqlodbc Dave Cramer www.postgres.rocks On Mon, 17 Nov 2025 at 11:52, Neeta Ghadge <[email protected]> wrote: > Hi, > Thank you for your prompt response. > It’s not SHOW command, rather it is *SET* that is causing session > pinning. I will try to find alternate approaches to avoid session pinning. > > > > > > *Thanks and Regards,* > > *Neeta Ghadge* > > > > *From:* Dave Cramer <[email protected]> > *Sent:* Monday, November 17, 2025 10:14 PM > *To:* Neeta Ghadge <[email protected]> > *Cc:* [email protected] > *Subject:* Re: Guidance on avoiding session pinning with psqlODBC and RDS > Proxy > > > > You don't often get email from [email protected]. Learn why this > is important <https://aka.ms/LearnAboutSenderIdentification; > > *CAUTION:* This email is from an external source. Please don’t open any > unknown links or attachments. > > Hi, > > > > Neeta, > > > > Talking to some folks at Amazon, they don't think it should pin. Can you > open a ticket with them? > > > > Dave Cramer > > www.postgres.rocks > > > > > > On Mon, 17 Nov 2025 at 11:21, Dave Cramer <[email protected]> > wrote: > > 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 <[email protected]> > 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) > > 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) > ^ permalink raw reply [nested|flat] 8+ messages in thread
* RE: Guidance on avoiding session pinning with psqlODBC and RDS Proxy 2025-11-16 14:53 Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 16:21 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 2025-11-17 16:44 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 2025-11-17 16:52 ` RE: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 17:01 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> @ 2025-11-17 17:12 ` Neeta Ghadge <[email protected]> 1 sibling, 0 replies; 8+ messages in thread From: Neeta Ghadge @ 2025-11-17 17:12 UTC (permalink / raw) To: Dave Cramer <[email protected]>; +Cc: pgsql-odbc Thank you 😊 I have created a new issue : https://github.com/postgresql-interfaces/psqlodbc/issues/143 Thanks and Regards, Neeta Ghadge From: Dave Cramer <[email protected]> Sent: Monday, November 17, 2025 10:32 PM To: Neeta Ghadge <[email protected]> Cc: [email protected] Subject: Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification; CAUTION: This email is from an external source. Please don’t open any unknown links or attachments. Ah, OK, I will have to change the driver. I think that is doable. Can you create an issue here https://github.com/postgresql-interfaces/psqlodbc Dave Cramer www.postgres.rocks<http://www.postgres.rocks/; On Mon, 17 Nov 2025 at 11:52, Neeta Ghadge <[email protected]<mailto:[email protected]>> wrote: Hi, Thank you for your prompt response. It’s not SHOW command, rather it is SET that is causing session pinning. I will try to find alternate approaches to avoid session pinning. Thanks and Regards, Neeta Ghadge From: Dave Cramer <[email protected]<mailto:[email protected]>> Sent: Monday, November 17, 2025 10:14 PM To: Neeta Ghadge <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification; CAUTION: This email is from an external source. Please don’t open any unknown links or attachments. Hi, Neeta, Talking to some folks at Amazon, they don't think it should pin. Can you open a ticket with them? Dave Cramer www.postgres.rocks<http://www.postgres.rocks/; On Mon, 17 Nov 2025 at 11:21, Dave Cramer <[email protected]<mailto:[email protected]>> wrote: 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<http://www.postgres.rocks/; On Mon, 17 Nov 2025 at 05:19, Neeta Ghadge <[email protected]<mailto:[email protected]>> 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) 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) 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 <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) ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy 2025-11-16 14:53 Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 16:21 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 2025-11-17 16:44 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 2025-11-17 16:52 ` RE: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 17:01 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> @ 2025-11-17 17:23 ` Jon Raiford <[email protected]> 2025-11-17 20:41 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 1 sibling, 1 reply; 8+ messages in thread From: Jon Raiford @ 2025-11-17 17:23 UTC (permalink / raw) To: Dave Cramer <[email protected]>; Neeta Ghadge <[email protected]>; +Cc: pgsql-odbc Here is the RDS documentation for this: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-proxy-pinning.html There was mention by OP of using InitQuery, but my understanding is that as long as the driver makes the set call that the pinning will happen regardless of what state the connection is currently in. My research also showed that the show command should not have affected the pinning. Jon From: Dave Cramer <[email protected]> Date: Monday, November 17, 2025 at 12:13 PM To: Neeta Ghadge <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Ah, OK, I will have to change the driver. I think that is doable. Can you create an issue here https://github.com/postgresql-interfaces/psqlodbc<https://github.com/postgresql-interfaces/psqlod...; Dave Cramer www.postgres.rocks<http://www.postgres.rocks; On Mon, 17 Nov 2025 at 11:52, Neeta Ghadge <[email protected]<mailto:[email protected]>> wrote: Hi, Thank you for your prompt response. It’s not SHOW command, rather it is SET that is causing session pinning. I will try to find alternate approaches to avoid session pinning. Thanks and Regards, Neeta Ghadge From: Dave Cramer <[email protected]> Sent: Monday, November 17, 2025 10:14 PM To: Neeta Ghadge <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification; CAUTION: This email is from an external source. Please don’t open any unknown links or attachments. Hi, Neeta, Talking to some folks at Amazon, they don't think it should pin. Can you open a ticket with them? Dave Cramer www.postgres.rocks<http://www.postgres.rocks; On Mon, 17 Nov 2025 at 11:21, Dave Cramer <[email protected]<mailto:[email protected]>> wrote: 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<http://www.postgres.rocks; On Mon, 17 Nov 2025 at 05:19, Neeta Ghadge <[email protected]<mailto:[email protected]>> 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<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) 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<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) ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy 2025-11-16 14:53 Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 16:21 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 2025-11-17 16:44 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 2025-11-17 16:52 ` RE: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 17:01 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Dave Cramer <[email protected]> 2025-11-17 17:23 ` Re: Guidance on avoiding session pinning with psqlODBC and RDS Proxy Jon Raiford <[email protected]> @ 2025-11-17 20:41 ` Dave Cramer <[email protected]> 0 siblings, 0 replies; 8+ messages in thread From: Dave Cramer @ 2025-11-17 20:41 UTC (permalink / raw) To: Jon Raiford <[email protected]>; +Cc: Neeta Ghadge <[email protected]>; pgsql-odbc Yes, I know how to fix it. Working on it. Dave Cramer www.postgres.rocks On Mon, 17 Nov 2025 at 12:23, Jon Raiford <[email protected]> wrote: > Here is the RDS documentation for this: > > > https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-proxy-pinning.html > > There was mention by OP of using InitQuery, but my understanding is that > as long as the driver makes the set call that the pinning will happen > regardless of what state the connection is currently in. My research also > showed that the show command should not have affected the pinning. > > Jon > > > *From: *Dave Cramer <[email protected]> > *Date: *Monday, November 17, 2025 at 12:13 PM > *To: *Neeta Ghadge <[email protected]> > *Cc: *[email protected] <[email protected]> > *Subject: *Re: Guidance on avoiding session pinning with psqlODBC and RDS > Proxy > > Ah, > > OK, I will have to change the driver. I think that is doable. > > Can you create an issue here > https://github.com/postgresql-interfaces/psqlodbc > > Dave Cramer > www.postgres.rocks > > > On Mon, 17 Nov 2025 at 11:52, Neeta Ghadge <[email protected]> > wrote: > > Hi, > Thank you for your prompt response. > It’s not SHOW command, rather it is *SET* that is causing session > pinning. I will try to find alternate approaches to avoid session pinning. > > > > > > *Thanks and Regards,* > > *Neeta Ghadge* > > > > *From:* Dave Cramer <[email protected]> > *Sent:* Monday, November 17, 2025 10:14 PM > *To:* Neeta Ghadge <[email protected]> > *Cc:* [email protected] > *Subject:* Re: Guidance on avoiding session pinning with psqlODBC and RDS > Proxy > > > > You don't often get email from [email protected]. Learn why this > is important <https://aka.ms/LearnAboutSenderIdentification; > > *CAUTION:* This email is from an external source. Please don’t open any > unknown links or attachments. > > Hi, > > > > Neeta, > > > > Talking to some folks at Amazon, they don't think it should pin. Can you > open a ticket with them? > > > > Dave Cramer > > www.postgres.rocks > > > > > > On Mon, 17 Nov 2025 at 11:21, Dave Cramer <[email protected]> > wrote: > > 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 <[email protected]> > 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) > > 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) > > ^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2025-11-17 20:41 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-11-16 14:53 Guidance on avoiding session pinning with psqlODBC and RDS Proxy Neeta Ghadge <[email protected]> 2025-11-17 16:21 ` Dave Cramer <[email protected]> 2025-11-17 16:44 ` Dave Cramer <[email protected]> 2025-11-17 16:52 ` Neeta Ghadge <[email protected]> 2025-11-17 17:01 ` Dave Cramer <[email protected]> 2025-11-17 17:12 ` Neeta Ghadge <[email protected]> 2025-11-17 17:23 ` Jon Raiford <[email protected]> 2025-11-17 20:41 ` Dave Cramer <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox