Time-series schemas over the PostgreSQL wire

Visualize QuestDB's Timestamp and Partition Columns

QuestDB is a columnar, append-only time-series database, and it speaks the PostgreSQL wire protocol. DbSchema connects with the standard PostgreSQL JDBC driver and puts a schema diagram, a SQL editor, and a data explorer on top of your table store.

  • Designated timestamp and partition columns on the diagram
  • SAMPLE BY, LATEST ON, and ASOF JOIN in the SQL editor
  • Spot-check freshly ingested rows in a paginated grid
  • Hand consumers a schema reference for every table
Free Community Edition No signup required 15-day Architect trial included
Free Download

Trusted by teams at

Pipelines Write the Tables
People Still Have to Read Them

In a QuestDB deployment, tables appear where the ingestion goes: sensors stream over the InfluxDB Line Protocol, services post to the REST API, and each table's designated timestamp quietly decides its partition layout. The engineers consuming that data see none of it.

DbSchema reads the store over the PostgreSQL wire endpoint and lays out every table, column type, and timestamp column where the whole team can look at it.

Query, Verify & Compare
QuestDB Tables Visually

Time-series SQL and schema tooling in one desktop client.

Run QuestDB time-series SQL in the DbSchema SQL editor
Time-Series SQL, First-Class

The SQL editor accepts QuestDB's extensions — SAMPLE BY, LATEST ON, ASOF JOIN — so you iterate on analytical queries and inspect column types in one place.

Browse QuestDB rows in the DbSchema data explorer
Check What Just Landed

Page through ingested rows with column-level filtering: confirm a row exists, verify timestamp precision after a write, all without a one-off query client.

Compare QuestDB table schemas across environments
Same Tables, Every Environment?

Compare table schemas across QuestDB instances — staging against production, region against region — and see each structural difference listed.

A Table Reference
Your Data Consumers Can Open

Generate HTML documentation listing each QuestDB table with its columns, data types, and designated timestamp column. Teams writing ingest code against the Line Protocol or the REST API read the expected schema in a browser — before the first malformed write.

Explore the Documentation Tool

HTML schema documentation generated from a QuestDB database

Port 8812: the Connection That Matters

QuestDB's PostgreSQL wire listener runs on port 8812 — not the usual PostgreSQL port. Select PostgreSQL as the database type and DbSchema downloads the JDBC driver automatically; the URL takes the form jdbc:postgresql://host:8812/qdb. The default credentials are username admin, password quest — production deployments should have changed them.

The REST API on port 9000 and the InfluxDB Line Protocol ingress on port 9009 are ingest-side interfaces; DbSchema talks only to the wire protocol endpoint at 8812. Driver details are on the QuestDB JDBC driver page.

See Your QuestDB Tables as a Schema

Community Edition is free; a 15-day Architect trial ships in the same download.

Teams working with QuestDB often use these engines too. Explore dedicated guides and JDBC setup for each.

Browse all 100+ supported databases