Documentation

Query CockroachDB

To query CockroachDB with Flux:

  1. Import the sql package.

  2. Use sql.from() and provide the following parameters:

    • driverName: postgres
    • dataSourceName: See data source name
    • query: PSQL query to execute
import "sql"

sql.from(
    driverName: "postgres",
    dataSourceName:
        "postgresql://username:password@localhost:26257/cluster_name.defaultdb?sslmode=verify-full&sslrootcert=certs_dir/cc-ca.crt",
    query: "SELECT * FROM example_table",
)

CockroachDB data source name

The postgres driver uses the following DSN syntax (also known as a connection string) to connect to CockroachDB :

postgres://username:password@localhost:26257/cluster_name.defaultdb?sslmode=verify-full&sslrootcert=certs_dir/cc-ca.crt

The postgres driver use the Go pq implementation to interact with CockroachDB.

CockroachDB to Flux data type conversion

sql.from() converts PostgreSQL and CockroachDB data types to Flux data types.

CockroachDB data typeFlux data type
INT, BIGINT, SMALLINT, TINYINT, INT2, INT4, INT8, SERIAL2, SERIAL4, SERIAL8int
FLOAT4, FLOAT8float
DATE, TIME, TIMESTAMPtime
BOOLbool
TEXTstring

All other CockroachDB data types are converted to strings.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value cachesβ€”making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2