↑↓ select↵ open⌫ change scopeOpen full search

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

Wiki / Protocol Messages

NoticeResponse

NoticeResponse is a backend protocol message. Identifies the message as a notice.

Reading PG 18·Select a recorded version

Direction
Backend → frontend
First wire field
Byte1('N')
Field entries
4
Documented flow contexts
Start-up; Simple Query; Function Call; COPY Operations; Asynchronous Operations
direction
B
manual path
/docs/18/protocol-message-formats.html
signature
NoticeResponse (B)

Definition PG 18

Byte1('N')

Identifies the message as a notice.

Int32

Length of message contents in bytes, including self.

The message body consists of one or more identified fields, followed by a zero byte as a terminator. Fields can appear in any order. For each field there is the following:

Byte1

A code identifying the field type; if zero, this is the message terminator and no string follows. The presently defined field types are listed in Section 54.8. Since more field types might be added in future, frontends should silently ignore fields of unrecognized type.

String

The field value.

Wire fields in documented order

PositionFormatMeaning
1Byte1('N')Identifies the message as a notice.
2Int32Length of message contents in bytes, including self.
3Byte1A code identifying the field type; if zero, this is the message terminator and no string follows. The presently defined field types are listed in Section 54.8 . Since more field types might be added in future, frontends should silently ignore fields of unrecognized type.
4StringThe field value.

Compare versions

Complete source facts

fields

map[description:Identifies the message as a notice. format:Byte1('N')], map[description:Length of message contents in bytes, including self. format:Int32], map[description:A code identifying the field type; if zero, this is the message terminator and no string follows. The presently defined field types are listed in Section 54.8 . Since more field types might be added in future, frontends should silently ignore fields of unrecognized type. format:Byte1], map[description:The field value. format:String]

Source references

Full definition and evidence JSON

Definition sources

center · PostgreSQL 18 · 555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f

Text language: en · 555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f