Records/golang/github.com/jackc/pgx/v5/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• v5.11.0 PASS 10 passing observations
• v5.10.0 FAIL
• v5.9.2 PASS 3 passing observations
• v5.7.6 PASS 6 passing observations
• v5.7.5 PASS 5 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×2 2026-08-26 → 2026-08-26

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release v5.9.2 → first failing release v5.10.0

  What differs across the boundary

  • github.com/jackc/pgpassfile v1.0.0 → — hypothesis
  • github.com/jackc/pgservicefile v0.0.0-20240606120523-5a60cdf6a761 → — hypothesis
  • golang.org/x/text v0.29.0 → — hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last failing release v5.10.0 → first passing release v5.11.0

  What differs across the boundary

  • github.com/jackc/pgpassfile v1.0.0 → — hypothesis
  • github.com/jackc/pgservicefile v0.0.0-20240606120523-5a60cdf6a761 → — hypothesis
  • github.com/jackc/puddle/v2 v2.2.2 → — hypothesis
  • github.com/stretchr/testify v1.11.1 → — hypothesis
  • golang.org/x/sync v0.17.0 → — hypothesis
  • golang.org/x/text v0.29.0 → — hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

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.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• github.com/jackc/pgx/v5 v5.10.0: pgxpool.Pool Built ? 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 Built ? 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 Built ? 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