From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Tue, 26 Apr 2011 00:13:53 +0000 (-0400)
Subject: Remove incorrect HINT for use of ALTER FOREIGN TABLE on the wrong relkind.
X-Git-Url: http://git.osdn.net/view?a=commitdiff_plain;h=6dab96abaa8bd6775658d26517e288f4d5f6448f;p=pg-rex%2Fsyncrep.git

Remove incorrect HINT for use of ALTER FOREIGN TABLE on the wrong relkind.

Per discussion, removing the hint seems better than correcting it because
the adjacent analogous cases in RenameRelation don't have any hints, and
nobody seems to have missed 'em.

Shigeru Hanada
---

diff --git a/src/backend/commands/tablecmds.c b/src/backend/commands/tablecmds.c
index 60eecb1497..437a6915b3 100644
--- a/src/backend/commands/tablecmds.c
+++ b/src/backend/commands/tablecmds.c
@@ -2247,8 +2247,7 @@ RenameRelation(Oid myrelid, const char *newrelname, ObjectType reltype)
 		ereport(ERROR,
 				(errcode(ERRCODE_WRONG_OBJECT_TYPE),
 				 errmsg("\"%s\" is not a foreign table",
-						RelationGetRelationName(targetrelation)),
-				 errhint("Use ALTER FOREIGN TABLE instead.")));
+						RelationGetRelationName(targetrelation))));
 
 	/*
 	 * Don't allow ALTER TABLE on composite types. We want people to use ALTER