-
+
User-Defined Aggregates
- Aggregate functions in
PostgreSQL
+ Aggregate functions in
PostgreSQL
are expressed in terms of state values
and state transition functions.
That is, an aggregate operates using a state value that is updated
aggregate to work on a data type for complex numbers,
we only need the addition function for that data type.
The aggregate definition would be:
-
+
CREATE AGGREGATE sum (complex)
(
the transition function is marked strict> (i.e., not to be called
for null inputs).
-
+
Another bit of default behavior for a strict> transition function
is that the previous state value is retained unchanged whenever a
transition function as strict; instead code it to test for null inputs and
do whatever is needed.
-
+
avg> (average) is a more complex example of an aggregate.
It requires
Here, the actual state type for any aggregate call is the array type
- having the actual input type as elements.
+ having the actual input type as elements. The behavior of the aggregate
+ is to concatenate all the inputs into an array of that type.
+ (Note: the built-in aggregate array_agg> provides similar
+ functionality, with better performance than this definition would have.)
pg_tablespace | {spcname,spcowner,spclocation,spcacl}
(1 row)
-SELECT attrelid::regclass, array_accum(atttypid)
+SELECT attrelid::regclass, array_accum(atttypid::regtype)
FROM pg_attribute
WHERE attnum > 0 AND attrelid = 'pg_tablespace'::regclass
GROUP BY attrelid;
- attrelid | array_accum
----------------+-----------------
- pg_tablespace | {19,26,25,1034}
+ attrelid | array_accum
+---------------+---------------------------
+ pg_tablespace | {name,oid,text,aclitem[]}
(1 row)