jochen
e1f5d4fdf0
The controller imports mesh-host/validate through a replace onto the forge that holds it, and every build — the build agent's go build in a fresh toolchain container, the Dockerfile's go mod download — would have fetched it through the public proxy and checksum database at build time: a merge breaking main on the network, the class Phase 1 removes. vendor/ is committed; go builds from it with nothing fetched, and refuses to build when it and go.mod disagree, so a pin moved without go mod vendor fails at once. The Dockerfile copies vendor/ and builds with GOPROXY=off.
12 lines
688 B
Go
12 lines
688 B
Go
// Package pgproto3 is an encoder and decoder of the PostgreSQL wire protocol version 3.
|
|
//
|
|
// The primary interfaces are Frontend and Backend. They correspond to a client and server respectively. Messages are
|
|
// sent with Send (or a specialized Send variant). Messages are automatically buffered to minimize small writes. Call
|
|
// Flush to ensure a message has actually been sent.
|
|
//
|
|
// The Trace method of Frontend and Backend can be used to examine the wire-level message traffic. It outputs in a
|
|
// similar format to the PQtrace function in libpq.
|
|
//
|
|
// See https://www.postgresql.org/docs/current/protocol-message-formats.html for meanings of the different messages.
|
|
package pgproto3
|