## TL;DR

When setting up an Estuary capture from Supabase, never use the pooled connection string: get the direct connection hostname with the pooler checkbox off, provision a dedicated IPv4 address, and confirm wal_level=logical with a REPLICATION role.

## Steps

1. When setting up an Estuary capture from Supabase, never use the pooled connection string: get the direct connection hostname with the pooler checkbox off, provision a dedicated IPv4 address, and confirm wal_level=logical with a REPLICATION role. If a second capture is added from the same database, give it its own replication slot instead of sharing the default flow_slot. In restricted setups create the publication and watermarks table manually with the SQL from the docs page before publishing the capture.

## When to use

You are seeing this: In restricted setups create the publication and watermarks table manually with the SQL from the docs page before publishing the capture. Use this skill when you run into "Estuary Supabase capture fails through the pooler: use direct connection".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.