Docs/Connections/Cloud Databases

Neon PostgreSQL Guide

Use this page when your PostgreSQL source or target is hosted in Neon.

This guide keeps the Neon-specific parts of the setup in one place:

  • project and branch connection details
  • required SSL behavior
  • Neon logical replication enablement for CDC source workflows

For the core workflow split, use:

Base setup

  1. Open the Neon Console.
  2. Select the project and branch that DBConvert Streams should use.

Neon Create Project

  1. Copy the PostgreSQL connection details.

Neon Connection Details

  1. Confirm the DBConvert Streams deployment can reach the Neon endpoint on port 5432.

Typical connection pattern:

postgres://user:[email protected]/dbname?sslmode=require

In DBConvert Streams, use the endpoint host, port 5432, username, password, database, and set SSL mode to require.

SSL requirements

Neon connections are SSL-oriented by default. Treat TLS as required unless your Neon setup explicitly documents something different.

In practice:

  • enable SSL/TLS in the DBConvert Streams connection
  • use a verification mode that matches your certificate policy
  • test the connection before creating a stream

CDC source preparation

If Neon is only a Load source or a target, the base PostgreSQL connection setup is enough.

If Neon is the CDC source, you must also enable logical replication in Neon first.

Typical flow:

  1. Open the Neon project settings.
  2. Enable logical replication for the project or branch.

Enable Logical Replication in Neon

  1. Confirm the chosen user has the privileges required by the PostgreSQL CDC workflow.
  2. Then complete the remaining steps in PostgreSQL CDC Source Configuration.

After enabling logical replication, verify:

SELECT name, setting
FROM pg_settings
WHERE name IN (
  'wal_level',
  'max_replication_slots',
  'max_wal_senders'
);

Check Replication Settings

Validation checklist

  1. Test the Neon connection from the Data Explorer sidebar (right-click → Test connection) or from the connection editor. If TLS fails, confirm SSL mode is set to require — Neon does not allow unencrypted connections.
  2. Open it in Data Explorer to confirm visible schemas and tables.
  3. If the workflow uses CDC, run SHOW wal_level and confirm it returns logical. If it shows replica, logical replication is not enabled in the Neon project settings.
  4. After Neon branch resets, compute restarts, or project-level changes, re-test the connection — Neon can reset replication state on these events.
PreviousDigitalOceanNextSupabase PostgreSQL