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.
28 lines
1016 B
Go
28 lines
1016 B
Go
// Package pgxpool is a concurrency-safe connection pool for pgx.
|
|
/*
|
|
pgxpool implements a nearly identical interface to pgx connections.
|
|
|
|
Creating a Pool
|
|
|
|
The primary way of creating a pool is with [pgxpool.New]:
|
|
|
|
pool, err := pgxpool.New(context.Background(), os.Getenv("DATABASE_URL"))
|
|
|
|
The database connection string can be in URL or keyword/value format. PostgreSQL settings, pgx settings, and pool settings can be
|
|
specified here. In addition, a config struct can be created by [ParseConfig].
|
|
|
|
config, err := pgxpool.ParseConfig(os.Getenv("DATABASE_URL"))
|
|
if err != nil {
|
|
// ...
|
|
}
|
|
config.AfterConnect = func(ctx context.Context, conn *pgx.Conn) error {
|
|
// do something with every new connection
|
|
}
|
|
|
|
pool, err := pgxpool.NewWithConfig(context.Background(), config)
|
|
|
|
A pool returns without waiting for any connections to be established. Acquire a connection immediately after creating
|
|
the pool to check if a connection can successfully be established.
|
|
*/
|
|
package pgxpool
|