↑↓ select ↵ open ⌫ change scope Open full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

Wiki / Logical Decoding Plugins

Logical Decoding Plugins

Compare versions

Logical decoding output plugins, formats, options and implementation-specific evidence.

Reading PostgreSQL 18.6.

2 core entries; 2 recorded in PostgreSQL 18.6.

RecordedFirst recordedInterface or attribute changeNo longer recorded

Squares indicate presence in sampled builds, not first introduction. Select a square for the same-version definition and sources.

Changes in PostgreSQL 18.6 · Export JSON

Logical-decoding plugin candidates

Current catalogue observation 2026-09-29 from pgext.universe. Extension versions, source metadata dates and declared PostgreSQL compatibility are independent of the selected core version. Catalogue classification does not establish capabilities or maintenance support.

11 directory rows.

Existing extensionCatalogued versionDeclared PG majorsMetadata checkedEvidence scopeCatalogued purpose
wal2json2.614, 15, 16, 17, 182026-08-30Primary documentation reviewed separately belowChanging data capture in JSON format
wal2mongo1.0.714, 15, 16, 17, 182026-08-30Catalogue candidate; interface unverifiedPostgreSQL logical decoding output plugin for MongoDB
decoderbufs3.6.014, 15, 16, 17, 182026-08-30Catalogue candidate; interface unverifiedLogical decoding plugin that delivers WAL stream changes using a Protocol Buffer format
decoder_raw1.014, 15, 16, 17, 182026-08-30Catalogue candidate; interface unverifiedOutput plugin for logical replication in Raw SQL format
test_decoding-14, 15, 16, 17, 18Not recordedCore interface; see versioned entrySQL-based test/example module for WAL logical decoding
pgoutput-14, 15, 16, 17, 18Not recordedCore interface; see versioned entryLogical Replication output plugin
jsoncdc0.1.0Unknown2026-08-30Catalogue candidate; interface unverifiedJSON logical decoding output plugin
replisome0.1Unknown2026-08-30Catalogue candidate; interface unverifiedLogical-decoding output plugin and Python consumer framework for streaming PostgreSQL row changes as JSON.
putpostlogic0.1.0Unknown2026-08-30Catalogue candidate; interface unverifiedUnreleased logical decoding output-plugin prototype that emits JSON changes through PostgreSQL, Kafka, or Nanomsg.
pboutput0.0.0Unknown2026-08-30Catalogue candidate; interface unverifiedBinary logical-decoding output plugin that encodes PostgreSQL changes as Protocol Buffers.
pg_turso1.0Unknown2026-08-30Catalogue candidate; interface unverifiedPostgres output plugin for replicating data to Turso.

Primary-source capability observations

Each statement applies to its named extension version and immutable source revision. Unlisted capabilities remain unknown. These are documentation observations, not runtime tests or current maintenance guarantees.

5 directory rows.

ExtensionReviewed versionCapabilityEvidence stateConditionsEvidence date and source
wal2json2.6Output granularityVerified in documentationFormat 1 emits one JSON object per transaction; format 2 emits one per tuple with optional transaction boundaries.2026-09-29 · 75629c2e1e81 · README.md
wal2json2.6Old row valuesConditionalUPDATE and DELETE old-row availability depends on replica identity.2026-09-29 · 75629c2e1e81 · README.md
wal2json2.6TRUNCATEConditionalThe actions option controls changes; format 1 excludes TRUNCATE for compatibility.2026-09-29 · 75629c2e1e81 · README.md
wal2json2.6Table and message filtersVerified in documentationOptions select or exclude tables, origins and logical-message prefixes.2026-09-29 · 75629c2e1e81 · README.md
wal2json2.6In-progress transaction streaming / two-phase decodingUnknownA streaming-protocol connection does not itself establish these capabilities; this documentation review does not verify them.2026-09-29 · 75629c2e1e81 · README.md

Reading this collection

Core output plugins use PostgreSQL-version evidence. Extension output formats and capabilities use independently dated, pinned project evidence. A catalog classification is not proof of protocol compatibility.