pulse
Prisma Pulse could not connect to the datasource db url. PostgreSQL returned the error: "Feature not supported: RDS Proxy currently doesn’t support the option idle_in_transaction_session_timeout.". This is probably not a problem with Prisma Pulse.
15 Replies
@Nurul (Prisma) just wondering if there is any known solution for this? Our AWS Solutions Architect says that even thought his says "This is probably not a problem with Prisma Pulse", he's pretty confident it is. Any help would be great;y appreciated.
We are currently on the Pro plan.
Hello @яσчαℓтℓя 👋
Can you please share your GitHub Handle or email id? This would help me in identifying your workspace/project details to check the logs.
I would recommend you to email us on [email protected] so that you can get dedicated support. We can continue conversation here as well if you prefer.
"Feature not supported: RDS Proxy currently doesn’t support the option idle_in_transaction_session_timeout."You got this error while you were trying to configure Pulse with your RDS connection string, right? Can you share the connection string format (After obfuscating username/password fields)? I want to see if you have specified any connection string paramaters.
Hi @Nurul (Prisma) - when setting up the account, I didn't link it to a GitHub since it's my client's account. The email address is [email protected]
The database URL is showing as: postgres://<username>:<password>@external-database-71e96cb8a99c079e.elb.eu-west-1.amazonaws.com/db_name
However, I did add the following parameters:
?schema=public&pool_timeout=10&sslmode=require
To confirm, this is happening on workspace named "Carhuna" in project named "Clumsy Lavender Elephant". The environment is named "Development", correct?
I am checking the logs on our side
From the logs I can see the same error that you reported:
I assume AWS RDS Proxy is enabled for your Postgres database, right?
https://aws.amazon.com/rds/proxy/
Amazon Web Services, Inc.
Scalable Applications - Amazon RDS Proxy - AWS
Amazon RDS Proxy improves database efficiency and application scalability by allowing applications to pool and share connections established with the database.
Yes all correct above
Is the idle_in_transaction_session_timeout issue something you've seen before?
I haven't seen anyone else reporting this same error before.
Can you temporarily disable RDS Proxy for your development environment and check if you get the same error? This would allow us to validate if the issue is caused due to compatibility issue between RDS Proxy and Pulse.
Yep, let me get back to you on this shortly
Hey @Nurul (Prisma) do you mean basically use the direct database URL connection string, as opposed to the AWS RDS Proxy one?
The strange thing is, I am able to connect to the RDS proxy instance via psql command after adding IP address to whitelist
Trying to add database URL (direct, no proxy) and getting other issues. Probably due to VPN access needed to access the database.
We are working on fixing this. I’ll ping you shortly once the fix is deployed.
Okay epic thank you
@яσчαℓтℓя Can you please try once more using the same database connection string that you were using before? RDS Proxy one. We just deployed a few changes.
Hey @Nurul (Prisma) getting this error now:
Prisma Pulse could not connect to the datasource db url. PostgreSQL returned the error: "permission denied for database carhuna". This is probably not a problem with Prisma Pulse.
It's odd because it works from my terminal, am able to connect with this connection string, which is the same one I am using in Prisma Pulse console
The permission denied error is caused when Pulse is trying to create a publication slot.
Can you try creating a publication slot using these instructions and provide the publication slot name while configuring Pulse.
Here are the detailed steps:
https://www.prisma.io/docs/pulse/database-setup/general-database-instructions#manage-the-tables-monitored-by-pulse
Prisma Pulse: General instructions | Prisma Documentation
Instructions to use your database with Prisma Pulse
If you specify the publication slot name, then Pulse won't try to create a default one (listening for changes on all tables). This would prevent the permission denied error
@яσчαℓтℓя Just checking to see if you are facing any issues. Let us know in case you are observing any errors.