Supabase: Allow using IPv4 #664
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rschu1ze
force-pushed
the
supabase-ipv4
branch
from
9c2a379 to
abc55b2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I tried to reproduce the new Supabase submission following #564 (comment)
I signed up for the service but then got timeouts when I tried to connect from local
psql. The reason is that Supabase by default requires IPv6. To fix that one can enable the IPv4 add-on (+4 $/month) or use a "connection pooler". This PR does the latter.After fixing this, the data import still failed with
... probably because I was only using the free plan.
Anyways, Supabase should now be a bit more reproducible than before.