From c232c8afa8dc398ee8ca3729630aba97c5622065 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 25 Sep 2006 15:17:34 +0000 Subject: Fix notice message from DROP FUNCTION IF EXISTS, and improve message for DROP AGGREGATE IF EXISTS. Per report from Teodor. --- src/backend/commands/aggregatecmds.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'src/backend/commands/aggregatecmds.c') diff --git a/src/backend/commands/aggregatecmds.c b/src/backend/commands/aggregatecmds.c index cb4dfee77e2..79a021cabc9 100644 --- a/src/backend/commands/aggregatecmds.c +++ b/src/backend/commands/aggregatecmds.c @@ -9,7 +9,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/commands/aggregatecmds.c,v 1.38 2006/07/27 19:52:04 tgl Exp $ + * $PostgreSQL: pgsql/src/backend/commands/aggregatecmds.c,v 1.39 2006/09/25 15:17:34 tgl Exp $ * * DESCRIPTION * The "DefineFoo" routines take the parse tree and pick out the @@ -219,8 +219,9 @@ RemoveAggregate(RemoveFuncStmt *stmt) { /* we only get here if stmt->missing_ok is true */ ereport(NOTICE, - (errmsg("aggregate %s does not exist ... skipping", - NameListToString(stmt->name)))); + (errmsg("aggregate %s(%s) does not exist ... skipping", + NameListToString(aggName), + TypeNameListToString(aggArgs)))); return; } -- cgit v1.2.3