Commit78b674b

committed

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

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

1 parent1945096 commit78b674bCopy full SHA for 78b674b

File tree

+15

-0

lines changed

+15

-0

lines changed

Lines changed: 9 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -212,3 +212,12 @@ SELECT '' AS ten, INTERVAL_TBL.*;`
`212`	`212`	`\| @ 5 mons 12 hours`
`213`	`213`	`(10 rows)`
`214`	`214`
	`215`	`+-- test avg(interval), which is somewhat fragile since people have been`
	`216`	`+-- known to change the allowed input syntax for type interval without`
	`217`	`+-- updating pg_aggregate.agginitval`
	`218`	`+select avg(f1) from interval_tbl;`
	`219`	`+ avg`
	`220`	`+-------------------------------------------------`
	`221`	`+ @ 4 years 1 mon 10 days 4 hours 18 mins 23 secs`
	`222`	`+(1 row)`
	`223`	`+`

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -60,3 +60,9 @@ SELECT '' AS fortyfive, r1., r2.`
`60`	`60`	`SET DATESTYLE='postgres';`
`61`	`61`
`62`	`62`	`SELECT''AS ten, INTERVAL_TBL.*;`
	`63`	`+`
	`64`	`+-- test avg(interval), which is somewhat fragile since people have been`
	`65`	`+-- known to change the allowed input syntax for type interval without`
	`66`	`+-- updating pg_aggregate.agginitval`
	`67`	`+`
	`68`	`+selectavg(f1)from interval_tbl;`

Comments

(0)