Confused about the Supabase email I have received regarding the connection string

Hello, I have received an email indificating that I have to update my connection string before 15th of January. My backend is on Java Spring Boot, so if I go to the Supabase dashboard for my database settings, and go to the Connection string -> JDBC settings, it shows the same url I am currently using: jdbc:postgresql://db.XXXXXXXX.supabase.co:5432/postgres?user=XXXX&password=XXXXX Do I have to change anything?
11 Replies
garyaustin
garyaustin2y ago
That is the direct database port and is not involved with the pooling port.
Shallz
ShallzOP2y ago
@garyaustin meaning I will be able to keep using it after 15th of january without having to perform any change?
garyaustin
garyaustin2y ago
correct.
Shallz
ShallzOP2y ago
kk cause the email also mentions:
Direct access to your database over IPv4 addresses is also deprecated. After January 15th, connecting directly to your database will only be supported over IPv6-compatible networks. To continue connecting over IPv4, use the Supavisor connection string.
Direct access to your database over IPv4 addresses is also deprecated. After January 15th, connecting directly to your database will only be supported over IPv6-compatible networks. To continue connecting over IPv4, use the Supavisor connection string.
But I was unsure if this was refering to the direct database connection I am using
garyaustin
garyaustin2y ago
That is something I've not seen asked. That is sort of what it sounds like.
Shallz
ShallzOP2y ago
@garyaustin How can I be sure? Is there someone from Supabase I can ask to?
garyaustin
garyaustin2y ago
I'll look around a bit and see if it is made clear. If not I'll ask them for clarifications.
garyaustin
garyaustin2y ago
GitHub
PGBouncer and IPv4 Deprecation · supabase · Discussion #17817
We recently announced Supavisor, our new connection pooler. Supavisor is now enabled for all projects created on or after Wednesday September 27th. All existing projects will have Supavisor enabled...
garyaustin
garyaustin2y ago
This seems pretty clear it does impact if you can't handle IPv6
With IPv4 addresses becoming increasingly scarce and cloud providers starting to charge for it, we won’t be assigning IPv4 addresses to Supabase projects from January 15th 2024. db.projectref.supabase.co will start resolving to a IPv6 address instead. If you plan on connecting to your database directly, you must ensure that your network can communicate over IPv6. Supavisor will continue to return IPv4 addresses, so you can update your applications to connect to Supavisor instead.
With IPv4 addresses becoming increasingly scarce and cloud providers starting to charge for it, we won’t be assigning IPv4 addresses to Supabase projects from January 15th 2024. db.projectref.supabase.co will start resolving to a IPv6 address instead. If you plan on connecting to your database directly, you must ensure that your network can communicate over IPv6. Supavisor will continue to return IPv4 addresses, so you can update your applications to connect to Supavisor instead.
Shallz
ShallzOP2y ago
When it says:
Supavisor will continue to return IPv4 addresses, so you can update your applications to connect to Supavisor instead.
Supavisor will continue to return IPv4 addresses, so you can update your applications to connect to Supavisor instead.
Does it refer to the connection string from the "Connection Pooling" section?¿
garyaustin
garyaustin2y ago
Yes that is what is implying.

Did you find this page helpful?