✳flâneur — a map of the web's best reading

PostgreSQL: Documentation: 17: 53.1. Overview

postgresql.org · 1,430 words · saved by 1 readers

The protocol has separate phases for startup and normal operation. In the startup phase, the frontend opens a connection to the server and authenticates itself to the satisfaction of the server. (This might involve a single message, or multiple messages depending on the authentication method being used.) If all goes well, the server then sends status information to the frontend, and finally enters normal operation. Except for the initial startup-request message, this part of the protocol is driven by the server. During normal operation, the frontend sends queries and other commands to the backend, and the backend sends back query results and other responses. There are a few cases (such as NOTIFY) wherein the backend will send unsolicited messages, but for the most part this portion of a session is driven by frontend requests. Termination of the session is normally by frontend choice, but can be forced by the backend in certain cases. In any case, when the backend closes the connection,

PostgreSQL: Documentation: 18: 54.1. Overview June 4, 2026: PostgreSQL 19 Beta 1 Released! Documentation → PostgreSQL 18 Supported Versions: Current ( 18 ) / 17 / 16 / 15 / 14 Development Versions: 19 / devel Unsupported versions: 13 / 12 / 11 / 10 / 9.6 / 9.5 / 9.4 / 9.3 / 9.2 / 9.1 / 9.0 / 8.4 / 8.3 / 8.2 54.1. Overview Prev Up Chapter 54. Frontend/Backend Protocol Home Next 54.1. Overview # 54.1.1. Messaging Overview 54.1.2. Extended Query Overview 54.1.3. Formats and Format Codes 54.1.4. Protocol Versions The protocol has separate phases for startup and normal operation. In the startu

Explore this link on the map →

saved by

related reading