EDB Postgres Advanced Server
The wait-event surface moved underneath you
The dynamic runtime instrumentation tools are deprecated at EDB Postgres Advanced Server 17 and absent from 18, and the wait-states extension that replaces them only has samples for the intervals it was loaded. A record with holes in it is not a record.
What goes wrong
A diagnostic surface that moved
Anything reading the old snapshot tables stops working at the next major version, and the replacement extension can only report on windows during which somebody had already loaded it.
Oracle-compatible catalogs, Postgres-shaped tools
In compatibility mode there are Oracle-style catalog views and syntax community PostgreSQL does not have. A collector that assumes the community shape reads the wrong thing, or nothing at all.
Two product lines and the community elephant
EDB Postgres Advanced Server on your own hardware, clusters provisioned under EDB Postgres AI, and community Postgres alongside both. The weekly health check covers one of the three.
What DBExplore does about it
The operational detail behind this: what crosses the boundary when the agent runs on your own hardware.
Sampling we own end to end
Active sessions and wait events are sampled and retained by DBExplore, so the evidence does not begin when an extension was installed or stop when that extension is deprecated.
One inventory across EDB and community Postgres
Engine, version, replication shape, pooler, backup tooling and extensions discovered on first connection. An EDB instance sits beside a managed one with the same history behind it.
Plan regression on a structural fingerprint
A regression means a plan change plus a real slowdown against the best prior plan, tracked identically whatever flavour is underneath, so a fleet-wide view compares like with like.
Air-gapped, and governed the same way
These fleets often sit on your own hardware behind an air gap. DBExplore deploys there, with the fail-closed policy gate, approval by default, a signed ledger, and an MCP interface for your own agents.
EDB Postgres Advanced Server: questions we get first
Do you publish a tested version matrix for EDB?
No. EDB Postgres Advanced Server is a reference engine here. Collectors that depend on a community catalog degrade and name the missing signal instead of inventing one, and we will not print a compatibility table we cannot stand behind.
Are you certified by, or partnered with, EDB?
No. There is no partnership, no certification and no named connector. DBExplore connects as a read-only Postgres role over the standard protocol, exactly as it does everywhere else.
How does the agent connect?
A container, Kubernetes deployment or sidecar, or native package next to your databases, using a read-only monitoring role over a small connection pool with short statement timeouts. No superuser.
Can DBExplore change anything without approval?
Not by default. Every tenant starts at approve. Disruptive actions always need two approvers, and every mutating action passes a fail-closed policy gate first.
Run DBExplore on your EDB Postgres Advanced Server.
We onboard teams in small batches. Tell us about your fleet and we will reach out when a seat opens. One email, no drip campaign.