Supabase Connection Pooler Deprecating Session Mode on Port 6543 on February 28, 2025

[w3b6x9]

If you're only using Transaction Mode on Connection Pooler port 6543 or already using Session Mode on port 5432 then no action is required.

On February 28, 2025, Supavisor (Supabase's Connection Pooler) is deprecating Session Mode on port 6543. After this date, port 6543 will only support Transaction Mode while port 5432 continues to support Session Mode.

We’re making this change because Session Mode is already available on port 5432 and this streamlines our connection pooler’s ports and their respective modes.

Required steps:

1. Update your application/database clients to use port 5432 for Session Mode.
2. In your project’s Database Settings (”Connection pooling configuration”), set “Pool Mode” to “Transaction” and click “Save” (please keep in mind that this will restart all your connections connected to the Pooler).

Please reach out to our support if you have any questions or concerns regarding this change.

[knandersen]

@w3b6x9 is this what's causing the latest version of self-hosted supabase to have trouble launching? I'm using the default settings and a clean docker container and getting this error:

Error response from daemon: driver failed programming external connectivity on endpoint supabase-pooler (c0c3928c50997ab417b481f357f1f0fa6093f0c77988c26710fdafd3e5831592): Bind for 0.0.0.0:5432 failed: port is already allocated

[w3b6x9]

@hauleth @chasers can you take a look at this?

[hauleth]

Are you sure that this error comes from Supavisor? How can I replicate your setup?

[w3b6x9]

driver failed programming external connectivity on endpoint supabase-pooler

looks like it's happening when spinning up

supabase/docker/docker-compose.yml

Line 474 in 257824e

container_name: supabase-pooler

which could involve supavisor.

[knandersen]

wiped my containers and couldn't recreate afterwards, so must have been an issue on my end. Apologies for the inconvenience.