Documentation

HAVING clause

The HAVING clause places conditions on results created by an aggregate operation on groups. The HAVING clause must follow the GROUP BY clause and precede the ORDER BY clause.

The WHERE clause filters rows based on specified conditions before the aggregate operation. The HAVING clause filters rows based on specified conditions after the aggregate operation has taken place.

Syntax

SELECT_clause FROM_clause [WHERE_clause] [GROUP_BY_clause] [HAVING_clause] [ORDER_BY_clause] 

Examples

Return rows with an aggregate value greater than a specified number

SELECT  MEAN("water_level") AS "mean_water_level", "location" FROM  "h2o_feet" GROUP BY  "location" HAVING  "mean_water_level" > 5

View example results

Return the average result greater than a specified number from a specific time range

SELECT  AVG("water_level") AS "avg_water_level",  "time" FROM  "h2o_feet" WHERE  time >= '2019-09-01T00:00:00Z' AND time <= '2019-09-02T00:00:00Z' GROUP BY  "time" HAVING  "avg_water_level" > 6.82 ORDER BY  "time"

View example results


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