Documentation

OFFSET and SOFFSET clauses

Use OFFSET to specify the number of rows to skip in each InfluxQL group before returning results. Use SOFFSET to specify the number of series to skip before returning results.

OFFSET clause

The OFFSET clause skips N rows in each InfluxQL group before returning results. Offsets honor row limits specified in the LIMIT clause and display the limited number of rows after the specified offset. Use LIMIT and OFFSET together to paginate query results.

Syntax

SELECT_clause FROM_clause [WHERE_clause] [GROUP_BY_clause] [ORDER_BY_clause] [LIMIT_clause] OFFSET N [SLIMIT_clause] [SOFFSET_clause]

Arguments

  • N: Number of rows to skip in each InfluxQL group before returning results.

Notable OFFSET clause behaviors

  • If there is no LIMIT clause in a query with an OFFSET clause, the query returns a single row per InfluxQL group at the specified offset.
  • If the query doesn’t include a GROUP BY clause, the entire result set is considered a single group and is returned in full.
  • If a query groups data by time, the offset is applied after aggregate and selector operations are applied to each time window.
  • If the WHERE clause includes a time range and the OFFSET clause causes InfluxQL to return points with timestamps outside of that time range, InfluxQL returns no results.

Examples

The following examples use the Home sensor sample data.

Return the nth row

Paginate results by 3 and return the 2nd page of results

Paginate results from each series by 3 and return the 2nd page of each series

SOFFSET clause

InfluxQL is being rearchitected to work with the InfluxDB 3 storage engine. This process is ongoing and some InfluxQL features, such as SOFFSET are still being implemented. For more information, see InfluxQL feature support.


Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, 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