Comments (20)
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.
I could do some troubleshooting if you tell me where I should find the logs for the sync attempts
from supabase.
Thanks for opening!
To confirm, you have 3 options to connect with AppSheet:
- Direct - 5432 - This is a direct connection to the database
- Pooler - Transaction - 6543 - This is a connection to your database through the Pooler where the connection is opened only for the lifetime of a transaction
- Pooler - Session - 5432 - This is a connection to your database through the Pooler where the connection is open until the client disconnects (so you are likely to hit connection limits here)
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!
from supabase.
That's kinda what I already knew about it.
The issue in this case is that I need transaction mode and it just doesn't work at all
from supabase.
"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 Expected behaviour
section expects Transaction mode to work the same as a direct connection but this is not the case. Session mode works the same as a direct connection.
from supabase.
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 Logs
by clicking Pooler.
from supabase.
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 though Supavisor was supposed to be a drop in replacement for PgBouncer.
If there is a difference in the way Supavisor exposed the database in comparison to PgBouncer, that should be the issue.
I'll do some troubleshooting and post the logs here.
Thanks for your help!
from supabase.
Hey @SkrOYC
That is a good point and I am not sure if the switch was called out as pgbouncer was set to transaction
mode by default. When you say AppSheet worked with pgBouncer was that after changing to session
mode as well?
from supabase.
Closing due to inactivity
from supabase.
Finding time to keep troubleshooting. This is still an issue.
In the meantime, I think we need to confirm from the people that was tied to the supavisor implementation if there is any difference in the way it behaves compared to pgbouncer that may make this not a 1:1 replacement to pgbouncer
from supabase.
Anyone has any idea about why the new Supavisor integration was not a 1:1 replacement to pgBouncer?
from supabase.
Btw @encima
When you say AppSheet worked with pgBouncer was that after changing to session mode as well?
AppSheet worked perfectly with pgBouncer in Transaction mode, CRUD operations were running quickly
from supabase.
"ClientHandler: socket closed with reason {:shutdown, :socket_closed}"
Same message again and again in the logs
from supabase.
I just found this message in the dashboard
Is it possible that the change to Supavisor is half done or it's expecting pgBouncer and the infrastructure is not there anymore?
@encima
from supabase.
Also found some of these under the "Postgres" logs:
from supabase.
@SkrOYC You likely need to upgrade your instance.
pgbouncer is not enabled on (almost) all instances but the user still exists in the DB.
"pending removal" means that the disabled pgbouncer will be removed completely from future instances but is not currently
To confirm, the switch to supavisor is complete but the phasing out of pgbouncer is not.
Supavisor is not a 1:1 replacement (both are open source so you are welcome to compare) but you can expect similar behaviours, if not the same. You can add "pgbouncer=true" to your Supavisor connection string to make the behaviour more similar which will disable prepared statements.
from supabase.
You likely need to upgrade your instance
Any clue on how to deal with it?
Also, we are connecting through the AppSheet connector for it, which takes the host:port, database name, user, password and nothing else
from supabase.
@SkrOYC you can see upgrades in the "Infrastructure" section in your project settings.
Ah, in that case you can use Supavisor transaction mode, session mode or a direct connection to the DB
from supabase.
in that case you can use Supavisor transaction mode, session mode or a direct connection to the DB
That's what we are trying to do, and worked perfectly before under pgBouncer and now it doesn't
you can see upgrades in the "Infrastructure" section in your project settings.
I can't see any upgrade options btw @encima
from supabase.
I can't see any upgrade options btw @encima
That should mean you are all good!
I see what you mean, now, sorry, I think I was confusing this with a different case.
Direct connections do work but I can reproduce your issue when using Supavisor and enforcing SSL
So, I can connect when using Supavisor, disabling SSL enforcement and not requiring SSL in AppSheet.
I will check with the pooler team if they can investigate more!
from supabase.
I can reproduce your issue when using Supavisor and enforcing SSL
SSL doesn't work but that's not a big issue for the time being, it's an AppSheet thing.
I can connect when using Supavisor, disabling SSL enforcement and not requiring SSL in AppSheet.
So can I, but after that I cannot add any table to any app nor sync anything on apps that were already working
from supabase.
Related Issues (20)
- Self-hosted no postgres log available HOT 14
- Inconsistent Typing for Joined Field in Supabase
- Missing documentation: Auth Hooks -> Send Email Webhbook HOT 1
- Impersonate user list limited to 10 records and search doesn't go beyond them HOT 1
- docker rootless: container supabase-vector exited (0) HOT 6
- Edge function error: http2 error: stream error received: unspecific protocol error detected HOT 2
- bug: pagination input box not working properly
- Supabase Wrapper > Firebase problem HOT 2
- When update not allowed by RLS, it passes without errr message HOT 7
- Java - Supabase Functions Integration HOT 3
- Image not showing HOT 3
- WORKER_ERROR - Getting this error while calling supabase edge function from postman HOT 1
- feat: Identify which email was verified during the two-step email update process HOT 1
- Self-Host: Storage Resumable TUS Upload to S3 throws AccessDenied HOT 1
- Confirmation Link Missing Port 8000 HOT 5
- Minor error in documentation for Prisma HOT 3
- Restoration of archived projects takes more than 12 hours HOT 1
- Docs snippet for confirm route assume redirect is a path instead of full URL HOT 1
- Email HOT 1
- Creating indexes on Supabase dashboard does not handle uppercase columns effectively
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from supabase.