Solution skill
Neon as logical replication publisher: enable once, carefully
Complete solution
Guide Neon as logical replication publisher: enable once, carefully: Enable logical replication on the project (Console project settings, CLI, or API). # Publishing logical replication from Neon ## The trap The toggle looks harmless in the Console. Use this when you hit exactly this in Neon as logical replication publisher. Not for different errors or different tools.
TL;DR: Enable logical replication on the project (Console project settings, CLI, or API). # Publishing logical replication from Neon ## The trap The toggle looks harmless in the Console. It is not: enabling logical replication changes
Fix
Enable logical replication on the project (Console project settings, CLI, or API). Expected: this specific failure stops.
Create the publication and replication slot on the publisher:. Expected: this specific failure stops.
hostname will not work. ## Checklist - Irreversible wal_level change: be sure before enabling. - Subscriber connection string: direct, no. Expected: this specific failure stops.
If you use IP Allow, add the subscriber's IPs to the list. - Tables need a replica identity (primary key) for updates/deletes to replicate. Expected: this specific failure stops.
Details
It is not: enabling logical replication changes wal_level from replica to logical Plan a maintenance window. Warn stakeholders: connections will drop and reconnect. 2. 3. ```sql CREATE PUBLICATION [pub-name] FOR TABLES [table1], [table2]; SELECT pgcreatelogicalreplicationslot('[slot-name]', 'pgoutput');
## When to use
You hit exactly this: Neon as logical replication publisher: enable once, carefully in Neon as logical replication publisher.
## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
## Compatibility
Neon as logical replication publisher.
## Root cause
and the slot name, because you created the slot manually.
## Edge cases
- # Publishing logical replication from Neon ## The trap The toggle looks harmless in the Console.
- for all databases in the project, it cannot be reverted, and it restarts all computes, dropping every active connection. ## The rule 1.Evidence
Neon's logical replication guide (verified live 2026-09-26): enabling changes wallevel from replica to logical for all databases, cannot be reverted, restarts all computes dropping connections; subscriber must use a direct connection string, not pooled; manual slot creation pairs with createslot=false on the subscription.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_9e9nK3cRqRykJlXgYoiypQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Neon as logical replication publisher: enable once, carefully <span>— Vectle</span></a>