Preamble
The PostgreSQL avg function returns the average value of the expression.
Syntax of avg function in PostgreSQL
SELECT avg(aggregate_expression)
FROM tables
[WHERE conditions];
Or the syntax of the avg function when grouping results into one or more columns:
SELECT expression1,2,..._n,
avg(aggregate_expression)
FROM tables
[WHERE conditions]
GROUP BY expression1,2,..._n;
Parameters and arguments of the function
- expression1, expression2,… expression_n – Expressions that are not enclosed in the function avg and must be included in the GROUP BY operator at the end of the SQL query.
- expression_expression – This is a column or expression to be averaged.
- tables – 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 avg 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 avg functions to understand how to use avg in PostgreSQL.
For example, you might be wondering what the average number of fields in an inventory table is.
SELECT avg(quantity) AS "Average Quantity"
FROM inventory;
In this example of the avg function, we used the alias avg(quantity) as “Average Quantity”. As a result, “Average Quantity” will appear as the field name when the result set returns.
Example using DISTINCT
You can use the DISTINCT operator in the avg function. For example, the SQL statement below returns the average of a unique quantity, where product_type is ‘Hardware’.
SELECT avg(DISTINCT quantity) AS "Average Quantity"
FROM inventory
WHERE product_type = 'Hardware';
If there were two quantities equal to 25, only one of these values would be used in the avg function.
Using formula
The expression contained in the avg function does not necessarily have to be a single field. You can also use a formula. For example, you may want to use the “Average Commission”.
SELECT avg(sales * 0.10) AS "Average Commission"
FROM orders;
Example using GROUP BY
You can also use the avg function to return the department and “Average Quantity” (the average number in the corresponding department). For example,
SELECT department, avg(quantity) AS "Average Quantity"
FROM inventory
GROUP BY department;
Since your SELECT operator has one column that is not encapsulated in the avg function, you should use the GROUP BY operator. Therefore, the department field should be specified in the GROUP BY section.
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
Smarter BFSI Database Operations: How Enteros Applies GenAI to Cloud FinOps and RevOps
- 14 January 2026
- Database Performance Management
Introduction Banks, financial institutions, insurers, and fintech organizations operate in one of the most complex and regulated technology environments in the world. Digital banking platforms, real-time payments, core transaction systems, fraud detection engines, regulatory reporting platforms, and customer engagement channels all depend on highly reliable database operations. As BFSI organizations modernize their technology stacks, database … Continue reading “Smarter BFSI Database Operations: How Enteros Applies GenAI to Cloud FinOps and RevOps”
How Enteros Uses AIOps to Transform Database Performance Management and Cloud FinOps
Introduction As enterprises accelerate cloud adoption, digital transformation has fundamentally reshaped how applications are built, deployed, and scaled. At the center of this transformation lies a critical but often overlooked layer: databases. Every transaction, customer interaction, analytics workflow, and AI model ultimately depends on database performance. Yet for many organizations, database performance management and cloud … Continue reading “How Enteros Uses AIOps to Transform Database Performance Management and Cloud FinOps”
AI-Driven Banking Operations: How Enteros Uses Generative AI and AIOps to Transform Performance
- 13 January 2026
- Database Performance Management
Introduction The banking and financial services industry is operating at a scale and speed never seen before. Digital banking platforms, real-time payments, open banking APIs, AI-powered risk engines, fraud detection systems, and regulatory reporting platforms have become mission-critical. Every customer interaction—from a mobile login to a high-value transaction—depends on complex, always-on technology systems. At the … Continue reading “AI-Driven Banking Operations: How Enteros Uses Generative AI and AIOps to Transform Performance”
From Listings to Leverage: How Enteros Drives Database Performance and FinOps Efficiency in Real Estate
Introduction The real estate industry has rapidly evolved from a traditionally relationship-driven business into a technology-intensive digital ecosystem. Modern real estate enterprises—spanning residential platforms, commercial real estate firms, property management companies, real estate SaaS providers, and proptech startups—are powered by sophisticated technology stacks. Behind online listings, virtual tours, pricing engines, tenant portals, CRM systems, transaction … Continue reading “From Listings to Leverage: How Enteros Drives Database Performance and FinOps Efficiency in Real Estate”