# Database support matrix The database engines Ptah supports, at what depth, and the operational differences to know before rollout. Source: https://docs.ptah.run/v0.8.1/databases/support-matrix/ Use this page to answer two lookup questions: whether Ptah has a dialect for an engine, and how much continuous testing stands behind a declared release line. The labels are testing guarantees, not runtime gates. Read [Support policy](../support-policy/) before using a line outside the declared set, and [Support evidence](../support-evidence/) to see how the claims are measured. ## Engines at a glance | Engine | Dialect (aliases) | URL schemes | Coverage | | --- | --- | --- | --- | | [PostgreSQL](../postgresql/) | `postgres` (`postgresql`, `pgx`) | `postgres://`, `postgresql://` | Primary first-party target with the broadest schema-object coverage. | | [SQLite](../sqlite/) | `sqlite` (`sqlite3`) | `sqlite://` | Supported for local workflows, examples, and lightweight test databases. | | [MySQL](../mysql/) | `mysql` | `mysql://` | Supported, with dialect-specific limitations. | | [MariaDB](../mysql/) | `mariadb` | `mariadb://` | Supported, with dialect-specific limitations. | | [SQL Server](../sqlserver/) | `sqlserver` (`mssql`, `tsql`, `sql-server`, `sql_server`) | `sqlserver://`, `mssql://` | Deliberately conservative portable subset. | | [CockroachDB](../distributed/) | `cockroachdb` (`cockroach`, `crdb`) | `cockroachdb://`, `crdb://` | PostgreSQL-compatible path with capability differences. | | [YugabyteDB](../distributed/) | `yugabytedb` (`yugabyte`, `ysql`) | `yugabytedb://`, `ysql://` | PostgreSQL-compatible path with capability differences. | | [ClickHouse](../clickhouse/) | `clickhouse` (`ch`) | `clickhouse://`, `ch://` | Capability-limited support. | | [Spanner (PostgreSQL interface)](../distributed/) | `spanner` (`cloudspanner`, `google-spanner`, `google_spanner`) | `spanner://` | Most conservative capability-limited support. | | [Oracle](../oracle/) | `oracle` | `oracle://` | Renders, plans, and reads a live catalog. | Accepted URL formats, and the difference between target, dev, shadow, and throwaway databases, are on [Database URLs and dev databases](../../concepts/database-urls-and-dev-databases/). Engines with no dialect entry are listed, with the reason and dated evidence, on [Support evidence](../support-evidence/#engines-with-no-ptah-dialect). ## Declared release lines Every engine ships several versions at once, and Ptah models each release line with its own capability preset. The table below is the declared set: the line, the preset it claims, how much testing stands behind that claim, and whether the capability probe measures it against a live server on every pull request. Declared is not the same as usable, and `Probed` is not the same as `Support`. A certified line can be unprobed when another CI path exercises it, or when the line needs no server at all — SQLite is compiled into the binary, so every `go test ./...` run exercises it. [Support policy](../support-policy/) defines the levels and explains what happens to a release absent from this table. The table is generated from the single declaration the CI matrix also reads, so the declared set cannot say one thing here and another in a workflow file. | Dialect | Release line | Support | Capability preset | Probed | | --- | --- | --- | --- | --- | | `postgres` | 18 | certified | `Postgres18` | yes | | `postgres` | 17 | certified | `Postgres17` | yes | | `postgres` | 16 | certified | `Postgres16` | yes | | `postgres` | 15 | certified | `Postgres16` | yes | | `postgres` | 14 | certified | `Postgres14` | yes | | `postgres` | 13 | legacy-tested | `Postgres13` | yes | | `mysql` | 26.7 | certified | `MySQL84` | yes | | `mysql` | 9.7 | certified | `MySQL84` | yes | | `mysql` | 8.4 | certified | `MySQL84` | yes | | `mariadb` | 12.3 | certified | `MariaDB1011` | yes | | `mariadb` | 11.8 | certified | `MariaDB1011` | yes | | `mariadb` | 11.4 | certified | `MariaDB1011` | yes | | `mariadb` | 10.11 | certified | `MariaDB1011` | yes | | `clickhouse` | 26.9 | certified | `ClickHouse2411` | yes | | `clickhouse` | 26.8 | certified | `ClickHouse2411` | yes | | `clickhouse` | 26.7 | certified | `ClickHouse2411` | yes | | `clickhouse` | 26.3 | certified | `ClickHouse2411` | yes | | `clickhouse` | 24.10 | legacy-tested | `ClickHouse24` | yes | | `sqlserver` | 17.0 (SQL Server 2025) | certified | `SQLServer2022` | yes | | `sqlserver` | 16.0 (SQL Server 2022) | certified | `SQLServer2022` | yes | | `sqlserver` | 15.0 (SQL Server 2019) | certified | `SQLServer2022` | yes | | `oracle` | 23 | certified | `Oracle23` | yes | | `oracle` | 21 | certified | `Oracle21` | yes | | `cockroachdb` | 26.3 | certified | `CockroachDB263` | yes | | `cockroachdb` | 26.2 | certified | `CockroachDB26` | yes | | `cockroachdb` | 25.4 | certified | `CockroachDB25` | yes | | `yugabytedb` | 2026.1 | certified | `YugabyteDB25` | yes | | `yugabytedb` | 2025.2 | certified | `YugabyteDB25` | yes | | `yugabytedb` | 2024.2 | certified | `YugabyteDB24` | yes | | `sqlite` | 3 | certified | `SQLite3` | yes | | `spanner` | 0 | best-effort | `SpannerPostgres` | yes | | `clickhouse` | 25.8 | best-effort | `ClickHouse2411` | no | Declared release lines: 32. Probed on every pull request: 31. Support levels across the 32 declared lines: 28 certified, 2 legacy-tested, 2 best-effort. Lines that are declared and not probed, and why: - `clickhouse` 25.8 — upstream support ended on 2026-08-29 (endoflife.date/clickhouse). Lines whose container tag does not name the line, so which patch it resolves to has to be read off the tag: - `sqlserver` 17.0, pinned as `mcr.microsoft.com/mssql/server:2025-latest`. - `sqlserver` 16.0, pinned as `mcr.microsoft.com/mssql/server:2022-latest`. - `sqlserver` 15.0, pinned as `mcr.microsoft.com/mssql/server:2019-latest`. - `oracle` 23, pinned as `gvenzl/oracle-free:slim`. - `oracle` 21, pinned as `gvenzl/oracle-xe:21-slim`. - `spanner` 0, pinned as `gcr.io/cloud-spanner-pg-adapter/pgadapter-emulator:v0.55.3`. ## Interpret the result The `Support` column answers how Ptah tests a release line. The capability profile answers what a particular server can do. Ptah does not read a support level to allow or refuse an operation. For a server you operate, ask Ptah which release line and capability preset it resolved: ```bash ptah db capabilities --db-url "$DATABASE_URL" ``` Read [Support policy](../support-policy/) for the level definitions and the behavior of undeclared versions. Read [Support evidence](../support-evidence/) for probe attribution, emulator limits, and the checks that keep this table tied to CI. Engine-specific capabilities and limitations live on the linked engine pages instead of being repeated here.