This tests the performance of pgx native, pgx through database/sql, pq through database/sql, [go-pg](github.com/go- pg/pg), and theoretical maximum PostgreSQL performance. It always uses prepared statements.

go_db_bench reads its configuration from the environment:
POSTGRES_SERVICE_HOST - defaults to empty
POSTGRES_SERVICE_PORT - 5432
PGPASSWORD - defaults to empty string
PGDATABASE - defaults to go_db_bench

go_db_bench includes tests selecting one value, one row, and multiple rows.

Example execution:

// Setup minkube and have postgresql pod running
$kubectl apply -f minikube/
$export POSTGRES_SERVICE_HOST=192.168.99.100  
$export POSTGRES_SERVICE_PORT=30032   
$make test

go_db_bench includes a simple HTTP server that serves JSON directly from PostgreSQL. This allows testing the performance of database drivers in a more real-world environment.

Example execution:

go build && PGHOST=/private/tmp ./go_db_bench

It exposes the following endpoints:

• /people/pgx-native - pgx through its native interface
• /people/pgx-stdlib - pgx through database/sql
• /people/pq - pq through database/sql

Start the server and use your favorite HTTP load tester to benchmark (I recommend siege or overload).

This benchmark includes a minimum PostgreSQL driver sufficient to establish a connection and prepare statements. Query execution is benchmarked by sending a []byte filled with the query command and reading until the ready for query message is received. This should be the theoretical best performance a Go PostgreSQL driver could achieve.

Caveat: The returned data is not checked or parsed. It is only read until the ready for query message is received. If an error occurs it may not be apparent which could cause the timing to be misleading.