November 14, 2024: PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 Released!
Supported Versions: Current (17) / 16 / 15 / 14 / 13
Development Versions: devel
Unsupported versions: 12 / 11 / 10 / 9.6 / 9.5 / 9.4 / 9.3 / 9.2 / 9.1 / 9.0 / 8.4 / 8.3 / 8.2 / 8.1 / 8.0 / 7.4 / 7.3 / 7.2 / 7.1
This documentation is for an unsupported version of PostgreSQL.
You may want to view the same page for the current version, or one of the other supported versions listed above instead.
PostgreSQL 8.0.26 Documentation
Prev Fast Backward Chapter 9. Functions and Operators Fast Forward Next

9.15. Aggregate Functions

Aggregate functions compute a single result value from a set of input values. Table 9-37 shows the built-in aggregate functions. The special syntax considerations for aggregate functions are explained in Section 4.2.7. Consult Section 2.7 for additional introductory information.

Table 9-37. Aggregate Functions

Function Argument Type Return Type Description
avg(expression) smallint, integer, bigint, real, double precision, numeric, or interval numeric for any integer type argument, double precision for a floating-point argument, otherwise the same as the argument data type the average (arithmetic mean) of all input values
bit_and(expression) smallint, integer, bigint, or bit same as argument data type the bitwise AND of all non-null input values, or null if none
bit_or(expression) smallint, integer, bigint, or bit same as argument data type the bitwise OR of all non-null input values, or null if none
bool_and(expression) bool bool true if all input values are true, otherwise false
bool_or(expression) bool bool true if at least one input value is true, otherwise false
count(*)   bigint number of input values
count(expression) any bigint number of input values for which the value of expression is not null
every(expression) bool bool equivalent to bool_and
max(expression) any numeric, string, or date/time type same as argument type maximum value of expression across all input values
min(expression) any numeric, string, or date/time type same as argument type minimum value of expression across all input values
stddev(expression) smallint, integer, bigint, real, double precision, or numeric double precision for floating-point arguments, otherwise numeric sample standard deviation of the input values
sum(expression) smallint, integer, bigint, real, double precision, numeric, or interval bigint for smallint or integer arguments, numeric for bigint arguments, double precision for floating-point arguments, otherwise the same as the argument data type sum of expression across all input values
variance(expression) smallint, integer, bigint, real, double precision, or numeric double precision for floating-point arguments, otherwise numeric sample variance of the input values (square of the sample standard deviation)

It should be noted that except for count, these functions return a null value when no rows are selected. In particular, sum of no rows returns null, not zero as one might expect. The coalesce function may be used to substitute zero for null when necessary.

Note: Boolean aggregates bool_and and bool_or correspond to standard SQL aggregates every and any or some. As for any and some, it seems that there is an ambiguity built into the standard syntax:

SELECT b1 = ANY((SELECT b2 FROM t2 ...)) FROM t1 ...;

Here ANY can be considered both as leading to a subquery or as an aggregate if the select expression returns 1 row. Thus the standard name cannot be given to these aggregates.

Note: Users accustomed to working with other SQL database management systems may be surprised by the performance characteristics of certain aggregate functions in PostgreSQL when the aggregate is applied to the entire table (in other words, no WHERE clause is specified). In particular, a query like

SELECT min(col) FROM sometable;

will be executed by PostgreSQL using a sequential scan of the entire table. Other database systems may optimize queries of this form to use an index on the column, if one is available. Similarly, the aggregate functions max() and count() always require a sequential scan if applied to the entire table in PostgreSQL.

PostgreSQL cannot easily implement this optimization because it also allows for user-defined aggregate queries. Since min(), max(), and count() are defined using a generic API for aggregate functions, there is no provision for special-casing the execution of these functions under certain circumstances.

Fortunately, there is a simple workaround for min() and max(). The query shown below is equivalent to the query above, except that it can take advantage of a B-tree index if there is one present on the column in question.

SELECT col FROM sometable ORDER BY col ASC LIMIT 1;

A similar query (obtained by substituting DESC for ASC in the query above) can be used in the place of max().

Unfortunately, there is no similarly trivial query that can be used to improve the performance of count() when applied to the entire table.

Prev Home Next
Array Functions and Operators Up Subquery Expressions