CodeSampleX

Recordsgolanggithub.com/jackc/pgx/v5v5.11.0

Which symbol ran where

Symbols × operating systems for this version. Cells drill into the package's compatibility cube.

6○ 62026-09-17
debian glibcubuntu glibc
github.com/jackc/pgx/v5.Conn 100%2 100%3
github.com/jackc/pgx/v5.NamedArgs 100%2 100%3
github.com/jackc/pgx/v5.QueryRewriter 100%2 100%4
github.com/jackc/pgx/v5.StrictNamedArgs 100%2 100%4
github.com/jackc/pgx/v5.StrictStructArgs 100%2 100%4
github.com/jackc/pgx/v5.StructArgs 100%2 80%5

Showing the environments with the most evidence.

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Environment detail

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

Environment Confidence Observations Verified Pass rate Peers Last seen
go 1.26 · Go · go · linux glibc · docker
Observations: PROJECT_LOAD 4✓ · PROJECT_TEST 4✓ — Usage: USED 4✓ — Verified: CONTRACT 6✓
MEDIUM 8 +4 6 100% 2 · 2✓ 2026-09-17
go 1.26 · Go · go · linux glibc
Observations: PROJECT_COMPILE 0✓ 3✕ · PROJECT_PROCESS 10✓ — Usage: USED 6✓
MEDIUM 13 +6 0 77% 2 2026-09-08

Symbols