Preamble
PostgreSQL HAVING statement is used in combination with GROUP BY statement to limit groups of returned strings only to those whose condition is TRUE.
The syntax for the HAVING statement in PostgreSQL
SELECT expression1_id, expression2_id,. expression_n_id,
aggregate_function
FROM tabs
[WHERE conds]
GROUP BY expression1_id, expression2_id,... expression_n_id
HAVING cond;
Statement parameters and arguments
- aggregate_function – This can be an aggregate function such as sum, count, min, max, or avg.
- expression1_id, expression_2id,… expression_n_id – Expressions which are not contained in the aggregate function and must be included in the GROUP BY operator.
- WHERE conds – Optional. These are conditions for selecting records.
- HAVING cond – This is another condition applied only to aggregate results to limit groups of returned lines. Only those groups whose condition is evaluated as TRUE will be included in the result set.
Example using the sum function
Let’s consider a HAVING example that uses the sum function.
You can also use the sum function to return a department and the sum(salary) function to that department. The PostgreSQL statement HAVING will filter the results so that only departments with a total salary greater than 25000 USD will be returned.
SELECT depart, sum(salary) AS "Salaries for the department"
FROM empls
GROUP BY depart
HAVING sum(salary) > 25000;
Example using count function
Let’s see how to use the HAVING operator with the count function.
You can use the count function to return a department and the number of employees (for that department) that have “Active” status. The PostgreSQL statement HAVING will filter the results so that only departments with a maximum of 35 employees will be returned.
SELECT department, count(*) AS "Number of employees"
FROM empls
WHERE status = 'Active'
GROUP BY depart
HAVING count(*) <= 35;
Example using min function
Let’s now see how to use the HAVING operator with the min function.
You can also use the min function to return the name of each department and the minimum wage in that department. PostgreSQL operator HAVING returns only those departments where the minimum wage is less than 36000 USD.
SELECT depart, min(salary) AS "Lowest salary".
FROM empls
GROUP BY depart
HAVING min(salary) < 36000;
Example using max function
Finally, let’s consider how to use the HAVING operator with the max function.
For example, you can also use the max function to return the name of each department and the maximum salary of the department. PostgreSQL statement HAVING will return only those departments whose maximum salary is more or equal to 31950 USD.
SELECT depart, max(salary) AS "Highest salary"
FROM empls
GROUP BY depart
HAVING max(salary) >= 31950;
PostgreSQL: Group By Having | Course
About Enteros
Enteros offers a patented database performance management SaaS platform. It proactively identifies root causes of complex business-impacting database scalability and performance issues across a growing number of clouds, RDBMS, NoSQL, and machine learning database platforms.
The views expressed on this blog are those of the author and do not necessarily reflect the opinions of Enteros Inc. This blog may contain links to the content of third-party sites. By providing such links, Enteros Inc. does not adopt, guarantee, approve, or endorse the information, views, or products available on such sites.
Are you interested in writing for Enteros’ Blog? Please send us a pitch!
RELATED POSTS
How Enteros Powers Telecom Growth with AI Performance Management and Cloud FinOps
- 9 March 2026
- Database Performance Management
Introduction The telecommunications industry is at the center of global digital transformation. From 5G rollouts and edge computing to streaming services, IoT connectivity, and real-time communication platforms, telecom companies are managing massive volumes of data and increasingly complex infrastructure. Behind every telecom service—voice calls, messaging, video streaming, mobile apps, and connected devices—there is a sophisticated … Continue reading “How Enteros Powers Telecom Growth with AI Performance Management and Cloud FinOps”
Eliminating Healthcare Data Bottlenecks: Enteros Database Software with AI SQL Root Cause Analysis
Introduction Healthcare organizations are under unprecedented pressure to deliver faster, smarter, and more reliable digital services. From electronic health records (EHR) and telemedicine platforms to AI-driven diagnostics and real-time patient monitoring, the healthcare ecosystem depends heavily on robust data infrastructure. At the center of this infrastructure are databases that store and process critical patient, clinical, … Continue reading “Eliminating Healthcare Data Bottlenecks: Enteros Database Software with AI SQL Root Cause Analysis”
How Enteros Transforms Financial Database Management with Predictive Cost Estimation
- 8 March 2026
- Database Performance Management
Introduction The financial sector is experiencing rapid digital transformation. From real-time trading platforms and digital banking applications to AI-driven risk analytics and regulatory reporting systems, financial institutions rely heavily on high-performance data infrastructure. At the heart of this infrastructure are databases that process enormous volumes of transactions, analytics workloads, and customer interactions every second. As … Continue reading “How Enteros Transforms Financial Database Management with Predictive Cost Estimation”
How to Align Insurance Growth Strategy with Database Performance and RevOps Intelligence
Introduction The insurance industry is undergoing a profound transformation. Digital policy management, real-time underwriting, AI-powered risk assessment, and omnichannel customer engagement are reshaping how insurers compete and grow. As organizations scale their digital capabilities, a critical yet often overlooked factor emerges: database performance and operational intelligence. Every insurance operation—from policy issuance and claims processing to … Continue reading “How to Align Insurance Growth Strategy with Database Performance and RevOps Intelligence”