diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-09-06 12:55:13 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-09-06 12:55:59 -0400 |
| commit | 2939f613fa91f12b43d51eb8c4e595d5164e5254 (patch) | |
| tree | 969a2673062f3eabad3d9f3796fba8f23facc73e /src | |
| parent | 1f8c163c5acdef34dff14615337332cecc21d70b (diff) | |
Fix misleading error message about inconsistent moving-aggregate types.
We reported the wrong types when complaining that an aggregate's
moving-aggregate implementation is inconsistent with its regular
implementation.
This was wrong since the feature was introduced, so back-patch
to all supported branches.
Jeff Janes
Discussion: https://postgr.es/m/CAMkU=1x808LH=LPhZp9mNSP0Xd1xDqEd+XeGcvEe48dfE6xV=A@mail.gmail.com
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/catalog/pg_aggregate.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/catalog/pg_aggregate.c b/src/backend/catalog/pg_aggregate.c index 40c56543ca0..61c20617c87 100644 --- a/src/backend/catalog/pg_aggregate.c +++ b/src/backend/catalog/pg_aggregate.c @@ -559,8 +559,8 @@ AggregateCreate(const char *aggName, ereport(ERROR, (errcode(ERRCODE_INVALID_FUNCTION_DEFINITION), errmsg("moving-aggregate implementation returns type %s, but plain implementation returns type %s", - format_type_be(aggmTransType), - format_type_be(aggTransType)))); + format_type_be(rettype), + format_type_be(finaltype)))); } /* handle sortop, if supplied */ |