Preamble
The min function in PostgreSQL returns the minimum value of the expression.
Syntax of the min function in PostgreSQL
SELECT min(aggregate_expression_id)
FROM tabs
[WHERE conds];
Or the syntax of the min function when grouping the results into one or more columns:
SELECT expression1_id,2_id,..._n_id,
min(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 min function and must be included in the GROUP BY operator at the end of the SQL query.
- aggregate_expression_id – This is a column or expression from which the minimum 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 conds – Optional. These are the conditions that must be met to select records.
The min 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
Consider some examples of min functions to understand how to use the min function in PostgreSQL.
For example, you can find out how the minimum value is in the inventory table.
SELECT min(quantity) AS "Lowest Quantity"
FROM inventory;
In this example of the min function, we called the expression min(quantity) as “Lowest Quantity”. As a result, “Lowest Quantity” will be displayed as the field name when the result set returns.
Example using GROUP BY
In some cases, you will need to use GROUP BY operator with min function.
For example, you can also use the min function to return values in the department field and the min(quantity) field from the inventory table.
SELECT department, min(quantity) AS "Lowest Quantity"
FROM inventory
GROUP BY department;
Since your SELECT operator has one column that is not encapsulated in the min function, you must use the GROUP BY operator. That is why the department field should 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
What Are the Biggest Database Performance Challenges Facing Modern Banks?
- 4 September 2026
- Database Performance Management
Modern banks face serious database performance challenges in banking, including transaction bottlenecks, growing data volumes, slow queries, legacy infrastructure, cloud complexity, security requirements, scalability problems, and limited real-time visibility. These issues can delay payments, affect digital banking experiences, increase operational risk, and raise infrastructure costs. Effective database monitoring and optimization help banks maintain reliable, responsive … Continue reading “What Are the Biggest Database Performance Challenges Facing Modern Banks?”
How Can Banks Improve Database Performance for High-Volume Financial Transactions?
Banks can improve database performance for high-volume financial transactions by reducing query latency, optimizing indexes, balancing workloads, monitoring database behavior in real time, and identifying bottlenecks before they affect customers. A strong bank database performance strategy combines observability, capacity planning, automation, and intelligent database performance optimization to keep payment, trading, lending, and digital banking systems … Continue reading “How Can Banks Improve Database Performance for High-Volume Financial Transactions?”
What Are the Most Common Database Performance Issues in Healthcare IT Systems?
The most common database performance issues in healthcare include slow SQL queries, poor indexing, locking, blocking, high concurrency, storage latency, resource contention, execution-plan changes, database growth, and workload spikes. EHR database performance issues can slow clinical workflows and patient-facing systems. Enteros helps healthcare IT teams detect anomalies, investigate root causes, optimize SQL, and improve database … Continue reading “What Are the Most Common Database Performance Issues in Healthcare IT Systems?”
How Can Hospitals Improve Database Performance for Faster EHR and Clinical Workflows?
Improving hospital database performance requires continuous monitoring, SQL optimization, indexing, workload analysis, anomaly detection, root cause analysis, and proactive capacity planning. Hospitals should also track latency, locking, storage I/O, and resource utilization across EHR and clinical systems. Enteros helps healthcare IT teams use AI-powered observability and performance intelligence to improve reliability, responsiveness, scalability, and healthcare … Continue reading “How Can Hospitals Improve Database Performance for Faster EHR and Clinical Workflows?”