Add regression test to catch future breakage of avg(interval). This

aggregate seems uniquely fragile, because it's the only one with an
agginitval that's at all likely to change in format.

diff --git a/src/test/regress/expected/interval.out b/src/test/regress/expected/interval.out
index 8a4eb275906a0c17e1b21540202d21abcaa286d2..ed16ada224f82f12f55ad60b24cf06f75f4e308c 100644 (file)
--- a/src/test/regress/expected/interval.out
+++ b/src/test/regress/expected/interval.out
@@ -212,3 +212,12 @@ SELECT '' AS ten, INTERVAL_TBL.*;
      | @ 5 mons 12 hours
 (10 rows)
 
+-- test avg(interval), which is somewhat fragile since people have been
+-- known to change the allowed input syntax for type interval without
+-- updating pg_aggregate.agginitval
+select avg(f1) from interval_tbl;
+                       avg                       
+-------------------------------------------------
+ @ 4 years 1 mon 10 days 4 hours 18 mins 23 secs
+(1 row)
+

diff --git a/src/test/regress/sql/interval.sql b/src/test/regress/sql/interval.sql
index 945eb08d60596084950c23b2f50b9727f69d796b..aa14cd3b094ae792c81b9ad34697b7a68281aaa5 100644 (file)
--- a/src/test/regress/sql/interval.sql
+++ b/src/test/regress/sql/interval.sql
@@ -60,3 +60,9 @@ SELECT '' AS fortyfive, r1.*, r2.*
 SET DATESTYLE = 'postgres';
 
 SELECT '' AS ten, INTERVAL_TBL.*;
+
+-- test avg(interval), which is somewhat fragile since people have been
+-- known to change the allowed input syntax for type interval without
+-- updating pg_aggregate.agginitval
+
+select avg(f1) from interval_tbl;