Recordsgolanggithub.com/jackc/pgx/v5failure issue
Failure signature
PROCESS_START process start failed Evidence gap ×7
Evidence quality: partial · structured-termination · gap diagnostic-missing · First recorded: 2026-08-27 · Last seen: 2026-09-14
sha256:c12549970456…
github.com/jackc/pgx/v5.Batch github.com/jackc/pgx/v5.Conn github.com/jackc/pgx/v5.ConnConfig github.com/jackc/pgx/v5.ConnectConfig github.com/jackc/pgx/v5.Deferrable github.com/jackc/pgx/v5.ErrNoRows github.com/jackc/pgx/v5.ErrTxClosed github.com/jackc/pgx/v5.ParseConfig github.com/jackc/pgx/v5.QueryExecModeExec github.com/jackc/pgx/v5.ReadOnly github.com/jackc/pgx/v5.ReadWrite github.com/jackc/pgx/v5.RepeatableRead github.com/jackc/pgx/v5.Row github.com/jackc/pgx/v5.Rows github.com/jackc/pgx/v5.Serializable github.com/jackc/pgx/v5.Tx github.com/jackc/pgx/v5.TxOptions github.com/jackc/pgx/v5/pgconn.CommandTag github.com/jackc/pgx/v5/pgconn.PgError github.com/jackc/pgx/v5/pgproto3.AuthenticationOk github.com/jackc/pgx/v5/pgproto3.CommandComplete github.com/jackc/pgx/v5/pgproto3.NewBackend github.com/jackc/pgx/v5/pgproto3.ParameterStatus github.com/jackc/pgx/v5/pgproto3.Query github.com/jackc/pgx/v5/pgproto3.ReadyForQuery github.com/jackc/pgx/v5/pgproto3.StartupMessage github.com/jackc/pgx/v5/pgproto3.Terminate
Where it was measured
PASS means the release recorded a passing observation at PROCESS_START and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=windows · runtime=go@1.26 ×4 2026-08-27 → 2026-09-14
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×1 2026-08-30 → 2026-08-31
- os=linux · runtime=go ×1 2026-08-27 → 2026-08-27
- os=linux · runtime=go@1.26 ×1 2026-08-27 → 2026-08-27
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
Moved: 3 · unchanged at every release: 4
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: diagnostic-missing.
- No release in this window recorded a passing observation at PROCESS_START.
- Releases in this window never measured at PROCESS_START: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/jackc/pgx/v5 v5.10.0: pgxpool.Pool This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/jackc/pgx/v5/pgxpool.Pool MIT-0 · 2026-08-28
- github.com/jackc/pgx/v5 v5.10.0: pgxpool.NewWithConfig This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/jackc/pgx/v5/pgxpool.NewWithConfiggo MIT-0 · 2026-08-28
- github.com/jackc/pgx/v5 v5.10.0: pgproto3.Terminate This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/jackc/pgx/v5/pgproto3.Terminate MIT-0 · 2026-08-28