Using AsyncPostgresSaver with Supabase's session pooler crashes with psycopg.OperationalError #2967
Unanswered
afnan-davia
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello all! I hope you are doing well. I am having issues with the psycopg.OperationalError and AsyncConnectionPool. I am using FastAPI in a container that is deployed on AWS AppRunner. Given that AppRunner doesn't have outgoing IPv6, I cannot directly use Supabase's postgres URL
postgresql://postgres:[YOUR-PASSWORD]@db.[PROJECT-ID].supabase.co:5432/postgres
.Therefore, I have to go through the Session pooler:
postgresql://postgres.[PROJECT-ID]:[YOUR-PASSWORD]@aws-0-eu-west-3.pooler.supabase.com:5432/postgres
.Here is how I instanciate my pool:
Unfortunately, I am randomly having the error
psycopg.OperationalError: consuming input failed: server closed the connection unexpectedly
when the code tries to executeI tried using:
but it still doesn't work. I looked on Supabase what connections are there and I can see 4 idle connections yet it crashed with the error mentioned above:
I would be really grateful for any help on this subject. This is the last step missing to put our chatbot with LangGraph's superpowers into production. Thank you very much for your time!
Beta Was this translation helpful? Give feedback.
All reactions