Wiki / Protocol Messages / Backend messages
BindComplete
BindComplete is a backend protocol message. Identifies the message as a Bind-complete indicator.
Reading PostgreSQL 18.6.
Description
BindComplete is a backend protocol message. Identifies the message as a Bind-complete indicator.
- Direction
- Backend → frontend
- First wire field
- Byte1('2')
- Field entries
- 2
- Documented flow contexts
- Extended Query
Usage
BindComplete (B)Framing and repetition
The complete definition below retains repetition, counts and conditional fields. A numbered table row is a documented field definition, not a fixed byte offset. Integer encodings and flow rules follow the same-version protocol chapter.
Wire fields in documented order
| Position | Format | Meaning |
|---|---|---|
| 1 | Byte1('2') | Identifies the message as a Bind-complete indicator. |
| 2 | Int32(4) | Length of message contents in bytes, including self. |
Manual definition
-
- Byte1('2')
-
Identifies the message as a Bind-complete indicator.
- Int32(4)
-
Length of message contents in bytes, including self.
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 17 → 18: unchanged.
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.