Records/golang/github.com/jackc/pgconn/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.

• v1.14.3 FAIL
• v1.9.1-0.20210724152538-d89c8390a530 not measured
• v1.9.0 not measured

Where it reproduced

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

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: 5 · 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 release in this window recorded a passing observation at PROJECT_PROCESS.
• Releases in this window never measured at PROJECT_PROCESS: 2
• No failure domain was inferred for this failure.

Published answers for the affected releases

• github.com/jackc/pgconn v1.14.3: parse postgresql connection config and inspect pgconn types with pgconn.ParseConfig 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. HOWpgconn.CommandTagpgconn.Configpgconn.NetworkAddresspgconn.ParseConfigpgconn.PgError MIT-0 · 2026-08-23