New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppSheet + Supabase: Since new Pooler, the connection is basically impossible to work with #23158
Comments
Thanks for opening!
AppSheet may recommend connection types but I would typically go through the Pooler's transaction (and modify timeouts if needed) rather than going through session as the client may keep connections open longer than needed so they are not freed for others. Read more here Let us know if that answers your question! |
That's kinda what I already knew about it. |
"Doesn't work at all" - Do you have more info on this? What are the logs on your instance reporting for the timeouts? What is the instance size and pool size you have configured? Your |
What I mean to what I expect is that from the client side we should see things working since Transaction mode has benefits on top of what Session mode can offer. I can connect using Session mode but if I change to port 6543 to not have issues with open connections (since the platform I'm using doesn't close them) it doesn't do anything other than authenticating. I can't sync data. |
Noted, thanks for the extra info. I have a gut feeling that the outcome of this will be: "AppSheet does not support transaction mode when connecting to Postgres" But, I am not sure so let's confirm this: you can check your Pooler logs in the dashboard under |
About the your first comment, my only knowledge about the way AppSheet works under the hood is that it was working wonderfully before with PgBouncer. I expect it to work as good as before with Supavisor but for some reason it doesn't. I'll do some troubleshooting and post the logs here. Thanks for your help! |
Hey @SkrOYC That is a good point and I am not sure if the switch was called out as pgbouncer was set to |
Closing due to inactivity |
Finding time to keep troubleshooting. This is still an issue. |
Bug report
Describe the bug
When using port "5432" things work with the obvious limits. AppSheet (a no-code platform owned by Google) opens a connection for each CRUD operation and this was solved by using the pooler on port "6543".
Everything worked perfect untill PgBouncer was left aside.
It justs seems using the pooler's port is not a transparent solution from the client's side.
Since this is a platform not managed by me I don't know the ins and outs of it, but I can say this was working perfectly before with PgBouncer.
To Reproduce
Use AppSheet and connect to the database using the Postgres connector with the 5432 port. Everything works perfect.
Change it to 6543 and you will face timeout issues. I can't add tables to my apps nor sync data on others apps already working with 5432.
Expected behavior
That the connection to the database under 6543 should work the same way 5432 does, being transparent on the client's side.
Additional info
This is a post in Appsheet's official community I made to promote Suabase and where users have been reporting the issue, which I was able to confirm
https://www.googlecloudcommunity.com/gc/Tips-Tricks/Updated-Supabase-mets-AppSheet/m-p/442135/highlight/true#M6685
The text was updated successfully, but these errors were encountered: