Movatterモバイル変換


[0]ホーム

URL:



Facebook
Postgres Pro
Facebook
Downloads
53.6. Message Data Types
Prev UpChapter 53. Frontend/Backend ProtocolHome Next

53.6. Message Data Types#

This section describes the base data types used in messages.

Intn(i)

Ann-bit integer in network byte order (most significant byte first). Ifi is specified it is the exact value that will appear, otherwise the value is variable. Eg. Int16, Int32(42).

Intn[k]

An array ofkn-bit integers, each in network byte order. The array lengthk 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. Ifs 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.

Byten(c)

Exactlyn bytes. If the field widthn is not a constant, it is always determinable from an earlier field in the message. Ifc is specified it is the exact value. Eg. Byte2, Byte1('\n').


Prev Up Next
53.5. Logical Streaming Replication Protocol Home 53.7. Message Formats
pdfepub
Go to Postgres Pro Standard 17
By continuing to browse this website, you agree to the use of cookies. Go toPrivacy Policy.

[8]ページ先頭

©2009-2025 Movatter.jp