Supavisor forces request to "postgres" database even when other database is specified
gitaugakwa opened this issue · comments
Bug report
- I confirm this is a bug with Supabase, not with my own application.
- I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
When attempting to connect to a database that is not named "postgres", supavisor forces the connection to the "postgres" database. This was previously mentioned in the issue #187 but has come up again. I had the following discussion on Discord.
To Reproduce
Create a connection to a database other than "postgres" through Supavisor.
Make a query through said connection.
Query would be performed on "postgres" database.
Expected behavior
Query to be performed on the database stated other than "postgres".
Screenshots
System information
- OS: Windows
- Version of supavisor: Version used on supabase.com as of 21/12/2023
- Version of Node.js: v18.17.1
Additional context
I am also seeing this. We have different databases that we manage via Prisma (that won't be public and we don't want to manage RLS rules on) and would love to be able to use pooling!
Got it ... we will fix.
Hey, just wanted to inform you that we've recently deployed a fix. We believe the problem should now be resolved. Please feel free to check and confirm whether everything is functioning as expected on your end