Documentation
¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func LogLevelFromEnv ¶
LogLevelFromEnv returns the tracelog.LogLevel from the environment variable PGX_LOG_LEVEL. By default this is info (tracelog.LogLevelInfo), which is good for development. For deployments, something like tracelog.LogLevelWarn is better choice.
func NewPGXPool ¶
func NewPGXPool(ctx context.Context, connString string, logger tracelog.Logger, logLevel tracelog.LogLevel, tracer trace.TracerProvider) (*pgxpool.Pool, error)
NewPGXPool is a PostgreSQL connection pool for pgx.
Usage: pgPool := database.NewPGXPool(context.Background(), "", &PGXStdLogger{Logger: slog.Default()}, tracelog.LogLevelInfo, tracer) defer pgPool.Close() // Close any remaining connections before shutting down your application.
Instead of passing a configuration explicitly with a connString, you might use PG environment variables such as the following to configure the database: PGDATABASE, PGHOST, PGPORT, PGUSER, PGPASSWORD, PGCONNECT_TIMEOUT, etc. Reference: https://www.postgresql.org/docs/current/libpq-envars.html
Types ¶
type PGX ¶
type PGX interface {
// BeginTx starts a transaction with txOptions determining the transaction mode. Unlike database/sql, the context only
// affects the begin command. i.e. there is no auto-rollback on context cancellation.
BeginTx(ctx context.Context, txOptions pgx.TxOptions) (pgx.Tx, error)
PGXQuerier
}
PGX limited interface with high-level API for pgx methods safe to be used in high-level business logic packages. It is satisfied by implementations *pgx.Conn and *pgxpool.Pool (and you should probably use the second one usually).
Caveat: It doesn't expose a method to acquire a *pgx.Conn or handle notifications, so it's not compatible with LISTEN/NOTIFY.
Reference: https://pkg.go.dev/github.com/jackc/pgx/v5
type PGXQuerier ¶
type PGXQuerier interface {
// Begin starts a transaction. Unlike database/sql, the context only affects the begin command. i.e. there is no
// auto-rollback on context cancellation.
Begin(ctx context.Context) (pgx.Tx, error)
// CopyFrom uses the PostgreSQL copy protocol to perform bulk data insertion.
// It returns the number of rows copied and an error.
//
// CopyFrom requires all values use the binary format. Almost all types
// implemented by pgx use the binary format by default. Types implementing
// Encoder can only be used if they encode to the binary format.
CopyFrom(ctx context.Context, tableName pgx.Identifier, columnNames []string, rowSrc pgx.CopyFromSource) (int64, error)
// Exec executes sql. sql can be either a prepared statement name or an SQL string. arguments should be referenced
// positionally from the sql string as $1, $2, etc.
Exec(ctx context.Context, sql string, arguments ...any) (pgconn.CommandTag, error)
// Query executes sql with args. If there is an error the returned Rows will be returned in an error state. So it is
// allowed to ignore the error returned from Query and handle it in Rows.
//
// For extra control over how the query is executed, the types QuerySimpleProtocol, QueryResultFormats, and
// QueryResultFormatsByOID may be used as the first args to control exactly how the query is executed. This is rarely
// needed. See the documentation for those types for details.
Query(ctx context.Context, sql string, args ...any) (pgx.Rows, error)
// QueryRow is a convenience wrapper over Query. Any error that occurs while
// querying is deferred until calling Scan on the returned Row. That Row will
// error with ErrNoRows if no rows are returned.
QueryRow(ctx context.Context, sql string, args ...any) pgx.Row
// SendBatch sends all queued queries to the server at once. All queries are run in an implicit transaction unless
// explicit transaction control statements are executed. The returned BatchResults must be closed before the connection
// is used again.
SendBatch(ctx context.Context, b *pgx.Batch) pgx.BatchResults
}
PGXQuerier interface with methods used for everything, including transactions.