Re: moving aggregate bad error message

2020-09-06 Thread Tom Lane
Jeff Janes writes: > Looking at the code, it seems we are testing rettype != finaltype, but > reporting aggmTransType and aggTransType. Why aren't we reporting what we > are testing? Silly thinko, apparently. Your fix looks right, will push. regards, tom lane

moving aggregate bad error message

2020-09-06 Thread Jeff Janes
I was wondering if I could just add minvfunc, and have the rest of the m* functions be assumed to be the same as their non-moving counterparts. Apparently the answer is 'no'. But in the process, I found a bad error message. When omitting mfinalfunc when there is a finalfunc, I get the error: "ER