Preamble
PostgreSQL MAX function returns the maximum value of the expression.
Syntax of the max function in PostgreSQL
SELECT max(aggregate_expression_id)
FROM tabs
[WHERE conds];
Or the syntax of the max function when grouping results into one or more columns:
SELECT expression1_id,2_id,..._n_id,
max(aggregate_expression_id)
FROM tabs
[WHERE conds]
GROUP BY expression1_id,2_id,..._n_id;
Parameters and arguments of the function
- expression1_id, expression2_id,… expression_n_id – Expressions that are not enclosed in the max function and must be included in the GROUP BY operator at the end of the SQL query.
- aggregate_expression_id – This is the column or expression from which the maximum value will be returned.
- tabs – These are the tables from which you want to get the records. At least one table must be specified in the FROM operator.
- WHERE conditions – Optional. These are the conditions that must be met to select records.
The max function can be used in the following PostgreSQL versions
PostgreSQL 11, PostgreSQL 10, PostgreSQL 9.6, PostgreSQL 9.5, PostgreSQL 9.4, PostgreSQL 9.3, PostgreSQL 9.2, PostgreSQL 9.1, PostgreSQL 9.0, PostgreSQL 8.4.
Single Expression Example
Let’s look at some examples of max functions to understand how to use max in PostgreSQL.
For example, you might want to select all entries with a maximum quantity from an inventory table as max(quantity) AS “Highest Quantity”.
SELECT max(quantity) AS "Highest Quantity"
FROM inventory;
In this example of the max function, we added the expression max(quantity) AS “Highest Quantity”. As a result, “Highest Quantity” will be displayed as the field name when the result set is returned.
Example using GROUP BY
In some cases, you will need to use the GROUP BY operator with the max function.
For example, you can also use the max function to return a department and the maximum quantity from the inventory table.
SELECT depart, max(quantity) AS "Highest Quantity"
FROM inventory
GROUP BY depart;
Since your SELECT operator has one column that is not encapsulated in the max function, you should use the GROUP BY operator. That’s why the department field shall be specified in the GROUP BY operator.
PostgreSQL: Calculating Min, Max & Average
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
Scaling Digital Banking with Confidence: AI SQL and Performance Intelligence by Enteros
- 5 February 2026
- Database Performance Management
Introduction Digital banking has moved from being a competitive differentiator to a baseline expectation. Customers now demand real-time payments, instant account access, personalized financial insights, always-on mobile experiences, and seamless digital onboarding—without delays, downtime, or friction. Behind these experiences lies an increasingly complex technology foundation. Core banking modernization, cloud-native digital platforms, open banking APIs, AI-powered … Continue reading “Scaling Digital Banking with Confidence: AI SQL and Performance Intelligence by Enteros”
Turning Database Performance into Revenue Intelligence: Enteros for US Financial Enterprises
Introduction In the US financial services market, technology performance is no longer just an IT concern—it is a direct driver of revenue, customer trust, and competitive advantage. Banks, fintechs, capital markets firms, insurers, and payments providers all operate in an environment defined by real-time transactions, digital-first customer expectations, regulatory scrutiny, and relentless pressure to improve … Continue reading “Turning Database Performance into Revenue Intelligence: Enteros for US Financial Enterprises”
AI Model–Powered Database Optimization for Real Estate: Performance Management and Cost Attribution with Enteros
- 4 February 2026
- Database Performance Management
Introduction The real estate sector is undergoing a profound digital transformation. Property management platforms, digital leasing systems, smart building technologies, tenant experience apps, AI-driven valuation models, ESG reporting tools, and real-time analytics now form the backbone of modern real estate enterprises. Behind every one of these systems lies a complex database ecosystem—supporting high transaction volumes, … Continue reading “AI Model–Powered Database Optimization for Real Estate: Performance Management and Cost Attribution with Enteros”
Accurate Cost Estimation for Telecom Databases: How Enteros Aligns AIOps and Performance Intelligence
Introduction Telecom organizations are operating at an unprecedented scale. 5G rollouts, digital service platforms, real-time billing systems, subscriber analytics, IoT connectivity, and AI-driven customer engagement have pushed data volumes and transaction complexity to new extremes. Yet while networks continue to modernize, database economics remain poorly understood. Most telecom leaders know their cloud bills are rising. … Continue reading “Accurate Cost Estimation for Telecom Databases: How Enteros Aligns AIOps and Performance Intelligence”