> For the complete documentation index, see [llms.txt](https://docs.postgresql.tw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.postgresql.tw/internals/protocol/protocol-message-types.md).

# 54.6. Message Data Types \#

This section describes the base data types used in messages.

Int\*`n`*(*`i`\*) : An *`n`*-bit integer in network byte order (most significant byte first). If *`i`* is specified it is the exact value that will appear, otherwise the value is variable. Eg. Int16, Int32(42).

Int\*`n`*\[*`k`\*] : An array of *`k`* *`n`*-bit integers, each in network byte order. The array length *`k`* is always determined by an earlier field in the message. Eg. Int16\[M].

String(*`s`*) : A null-terminated string (C-style string). There is no specific length limitation on strings. If *`s`* is specified it is the exact value that will appear, otherwise the value is variable. Eg. String, String("user").

```
### Note

*There is no predefined limit* on the length of a string
that can be returned by the backend. Good coding strategy for a frontend
is to use an expandable buffer so that anything that fits in memory can be
accepted. If that's not feasible, read the full string and discard trailing
characters that don't fit into your fixed-size buffer.
```

Byte\*`n`*(*`c`\*) : Exactly *`n`* bytes. If the field width *`n`* is not a constant, it is always determinable from an earlier field in the message. If *`c`* is specified it is the exact value. Eg. Byte2, Byte1('\n').

***

原文：[PostgreSQL 18.6 Documentation](https://www.postgresql.org/docs/18/protocol-message-types.html)（英文原文，待翻譯）


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.postgresql.tw/internals/protocol/protocol-message-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.