Neon

• pgstreamsource refers to the user provided in the pgstream source URL.
• pgstreamtarget refers to the user provided in the pgstream target URL.

​

Snapshots

​

From Neon Database (Snapshots)

​

Quick Checklist

• Create a source user (pgstreamsource) with access to required schemas/tables.
• For roles without passwords → no special config needed.
• For roles with passwords → must use the neondb_owner superuser.
• Update YAML config with correct snapshot settings.

​

Steps

1. User privileges Ensure the pgstreamsource user (from the pgstream source URL) owns the database schema and tables you want to snapshot.
2. Roles handling
   • No roles → no changes required.
   • Roles without passwords → no changes required.
   • Roles with passwords → must use the neondb_owner user.
   ⚠️ Only the neondb_owner user has access to the pg_authid table required for snapshotting roles with passwords. Without this, you’ll see:
   pg_dumpall: error: query failed: ERROR:  permission denied for table pg_authid
   
3. Config when not snapshotting roles If roles are disabled or not manually managed, add the following to avoid failures:
   snapshot:
     schema:
       pgdump_pgrestore:
         roles_snapshot_mode: "disabled"
         no_owner: true
         no_privileges: true
   
   Example full configuration:
   source:
     postgres:
       url: "postgresql://pgstreamsource:password@<neon-host>:5432/db?sslmode=require"
       mode: snapshot
       snapshot:
         mode: full # schema + data
         tables: ["public.*"] # all tables in the public schema
         schema:
           mode: pgdump_pgrestore
           pgdump_pgrestore:
             roles_snapshot_mode: "disabled"
             no_owner: true
             no_privileges: true
   

​

To Neon Database (Snapshots)

​

Quick Checklist

• Create a target user (pgstreamtarget) for the pgstream target URL.
• Grant privileges for schema/database ownership.
• Grant optional privileges depending on features (create DB, create roles).
• Use disable_triggers: false (required for all non-neon users).

​

Steps

• Schema ownership
  ALTER DATABASE db OWNER TO pgstreamtarget;
  ALTER SCHEMA public OWNER TO pgstreamtarget;
  
• Database creation (if create_target_db is enabled)
  ALTER ROLE pgstreamtarget CREATEDB;
  
• Role creation (if roles_snapshot_mode is enabled/no_passwords)
  ALTER ROLE pgstreamtarget CREATEROLE;
  
  ⚠️ pgstreamtarget must already hold any privileges it assigns (e.g., REPLICATION).
• Disable triggers (required for Neon) ⚠️ Not even the pseudo-superuser neondb_owner user can set session_replication_role on Neon databases.
  target:
    postgres:
      disable_triggers: false # Required for neon target databases
  
  ❌ If using disable_triggers: true, pgstream will fail with:
  permission denied to set parameter "session_replication_role"
  

​

Replication

​

From Neon Database (Replication)

​

Quick Checklist

• Ensure logical replication is enabled on your Neon database.
• Use the neondb_owner user for initialization (only user with event trigger privileges).
• Optionally use a different pgstreamsource user for streaming.

​

Steps

1. Enable logical replication Logical replication requires wal_level to be set to logical. Check current setting:
   SHOW wal_level;
   
   If not set to logical, update it: Neon enables logical replication by default on most databases. If you see wal_level = replica, you can enable logical replication through the Neon Console:
   1. Go to your project in the Neon Console
   2. Navigate to Settings → Replication
   3. Enable Logical replication
   4. No restart is required - Neon handles this automatically
   Alternatively, you can enable it via the Neon API or contact Neon support.
2. Replication phases
   • Initialization → requires elevated privileges to create schemas, event triggers, and replication slots.
   • Streaming → can use a dedicated pgstreamsource user.

​

Initialization

• Creates pgstream schema
• Creates replication slot (if missing)
• Creates event triggers/functions for schema changes

source:
  postgres:
    url: "postgresql://neondb_owner:password@<neon-host>:5432/db?sslmode=require"
    mode: replication

​

Streaming

• Keep using neondb_owner, or
• Transfer ownership to a dedicated pgstreamsource role.

-- Allow ownership transfer
GRANT pgstreamsource TO current_user;

-- Transfer ownership
ALTER DATABASE db OWNER TO pgstreamsource;
ALTER SCHEMA pgstream OWNER TO pgstreamsource;
ALTER SCHEMA <schema> OWNER TO pgstreamsource;
ALTER TABLE pgstream.schema_log OWNER TO pgstreamsource;
ALTER TABLE pgstream.table_ids OWNER TO pgstreamsource;
ALTER SEQUENCE pgstream.xid_serial OWNER TO pgstreamsource;

-- Replication privileges
ALTER ROLE pgstreamsource REPLICATION;

​

To Neon Database (Replication)

​

Quick Checklist

• Ensure pgstreamtarget has schema/database ownership.
• If combined with snapshot → follow Snapshot target requirements.

​

Steps

ALTER DATABASE db OWNER TO pgstreamtarget;
ALTER SCHEMA <schema> OWNER TO pgstreamtarget;

​

Troubleshooting