All Products
Search
Document Center

PolarDB:Push down a condition from the HAVING clause to the WHERE clause

Last Updated:Jun 12, 2024

PolarDB allows you to push down a condition from the HAVING clause of an SQL query to the WHERE clause. To improve query performance, you can transform complex SQL queries to push down conditions that are suitable for earlier filtering from the HAVING clause to the WHERE clause.

Prerequisites

You cluster runs PolarDB for MySQL 8.0 whose revision version is 8.0.2.2.10 or later. For information about how to query the version of a cluster, see the "Query the engine version" section of the Engine versions topic.

Limits

  • If a condition (or part of a condition) depends only on the fields used in the GROUP BY clause, or fields that are identical to the grouped fields, the condition can be pushed down from the HAVING clause to the WHERE clause.

  • Aggregate functions cannot be pushed down.

Background

HAVING clauses are used in many complex queries to filter grouped results. In most cases, conditions in the HAVING clause are applied to the grouped data that results from the GROUP BY operation. You can push down conditions in the HAVING clause that are suitable for earlier filtering to the WHERE clause. This minimizes the amount of data processed in the later stages of the query and significantly improves the performance and efficiency of the query.

Usage

You can use the loose_polar_optimizer_switch parameter to enable condition pushdown from the HAVING clause to the WHERE clause. You can use the loose_having_cond_pushdown_mode parameter to specify the nodes on which you want to enable the feature. For information about parameter configuration, see Configure cluster and node parameters.

Parameters

Parameter

Level

Description

loose_polar_optimizer_switch

Global and session

Specifies whether to enable condition pushdown from the HAVING clause to the WHERE clause. Valid values:

  • having_cond_pushdown=ON (default): enables condition pushdown from the HAVING clause to the WHERE clause.

  • having_cond_pushdown=OFF: disables condition pushdown from the HAVING clause to the WHERE clause.

loose_having_cond_pushdown_mode

Global

Specifies the type of nodes on which you want to enable condition pushdown from the HAVING clause to the WHERE clause. Valid values:

  • REPLICA_ON (default): enables condition pushdown from the HAVING clause to the WHERE clause only on read-only nodes.

  • ON: enables condition pushdown from the HAVING clause to the WHERE clause on all nodes.

  • OFF: disables condition pushdown from the HAVING to the WHERE clause on all nodes.

Examples

Push down a condition from the HAVING clause to the WHERE clause.

Example 1:

SELECT t1.a,MAX(t1.b)
FROM t1
GROUP BY t1.a
HAVING (t1.a>2) AND (MAX(c)>12);

Query syntax after transformation:

SELECT t1.a,MAX(t1.b)
FROM t1
WHERE (t1.a>2)
GROUP BY t1.a
HAVING (MAX(c)>12);

Example 2:

SELECT t1.a,MAX(t1.b),t1.c
FROM t1
GROUP BY t1.a
HAVING ((t1.a=t1.c) AND (t1.a>1)) OR ((t1.a<3) AND (t1.c>3));

Query syntax after transformation:

SELECT t1.a,MAX(t1.b),t1.c
FROM t1
WHERE ((t1.a=t1.c) AND (t1.a>1)) OR (t1.a<3)
GROUP BY t1.a
HAVING ((t1.a=t1.c) AND (t1.a>1)) OR ((t1.a<3) AND (t1.c>3));