Documentation → PostgreSQL 7.2

Supported Versions: Current (17) / 16 / 15 / 14 / 13

Development Versions: devel

Unsupported versions: 12 / 11 / 10 / 9.6 / 9.5 / 9.4 / 9.3 / 9.2 / 9.1 / 9.0 / 8.4 / 8.3 / 8.2 / 8.1 / 8.0 / 7.4 / 7.3 / 7.2 / 7.1

This documentation is for an unsupported version of PostgreSQL.
You may want to view the same page for the current version, or one of the other supported versions listed above instead.

PostgreSQL 7.2.8 Documentation
Prev	Chapter 4. Frontend/Backend Protocol	Next

4.3. Message Data Types

This section describes the base data types used in messages.

Intn(i): An n bit integer in network byte order. If i is specified it is the literal value. Eg. Int16, Int32(42).
LimStringn(s): A character array of exactly n bytes interpreted as a null-terminated string. The zero-byte is omitted if there is insufficient room. If s is specified it is the literal value. Eg. LimString32, LimString64("user").
String(s): A conventional C null-terminated string with no length limitation. If s is specified it is the literal value. 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.
Byten(c): Exactly n bytes. If c is specified it is the literal value. Eg. Byte, Byte1('\n').

Prev	Home	Next
Protocol	Up	Message Formats