↑↓ select ↵ open ⌫ change scope Open full search

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

Wiki / Protocol Messages / Logical replication formats

Delete (logical replication)

Logical replication Delete format. Identifies the message as a delete message.

Reading PostgreSQL 18.6.

Description

Logical replication Delete format. Identifies the message as a delete message.

Layer
Logical replication payload; distinct from the frontend/backend message envelope
First field
Byte1('D')

Usage

Delete

Protocol context

This section describes the detailed format of each logical replication message. These messages are either returned by the replication slot SQL interface or are sent by a walsender. In the case of a walsender, they are encapsulated inside replication protocol WAL messages as described in Section 54.4 , and generally obey the same message flow as physical replication. The following messages (Stream Start, Stream Stop, Stream Commit, and Stream Abort) are available since protocol version 2. The following messages (Begin Prepare, Prepare, Commit Prepared, Rollback Prepared, Stream Prepare) are available since protocol version 3. The following message parts are shared by the above messages.

Fields in documented order

PositionFormatMeaning
1Byte1('D')Identifies the message as a delete message.
2Int32 (TransactionId)Xid of the transaction (only present for streamed transactions). This field is available since protocol version 2.
3Int32 (Oid)OID of the relation corresponding to the ID in the relation message.
4Byte1('K')Identifies the following TupleData submessage as a key. This field is present if the table in which the delete has happened uses an index as REPLICA IDENTITY.
5Byte1('O')Identifies the following TupleData message as an old tuple. This field is present if the table in which the delete happened has REPLICA IDENTITY set to FULL.
6TupleDataTupleData message part representing the contents of the old tuple or primary key, depending on the previous field.

Manual definition

Byte1('D')

Identifies the message as a delete message.

Int32 (TransactionId)

Xid of the transaction (only present for streamed transactions). This field is available since protocol version 2.

Int32 (Oid)

OID of the relation corresponding to the ID in the relation message.

Byte1('K')

Identifies the following TupleData submessage as a key. This field is present if the table in which the delete has happened uses an index as REPLICA IDENTITY.

Byte1('O')

Identifies the following TupleData message as an old tuple. This field is present if the table in which the delete happened has REPLICA IDENTITY set to FULL.

TupleData

TupleData message part representing the contents of the old tuple or primary key, depending on the previous field.

The Delete message may contain either a 'K' message part or an 'O' message part, but never both of them.

Related entries

Documentation and source

Source build
Version
18.6
Build
https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2
Source fingerprint
555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f

Compare versions

PostgreSQL 14 → 15: changed.

--- PostgreSQL 14
+++ PostgreSQL 15
@@ -6,11 +6,11 @@
     },
     {
       "description": "Xid of the transaction (only present for streamed transactions). This field is available since protocol version 2.",
-      "format": "Int32"
+      "format": "Int32 (TransactionId)"
     },
     {
-      "description": "ID of the relation corresponding to the ID in the relation message.",
-      "format": "Int32"
+      "description": "OID of the relation corresponding to the ID in the relation message.",
+      "format": "Int32 (Oid)"
     },
     {
       "description": "Identifies the following TupleData submessage as a key. This field is present if the table in which the delete has happened uses an index as REPLICA IDENTITY.",

Compares recorded interfaces and attributes. Source fingerprints and build metadata are excluded; an absent sample is not proof of the introduction or removal release.

Related entries

Export JSON · Back to Protocol Messages · Recorded in PostgreSQL 10 through 20; the first sample is not necessarily its introduction.