Re: wrong hint message for ALTER FOREIGN TABLE - Mailing list pgsql-hackers

From Tom Lane
Subject Re: wrong hint message for ALTER FOREIGN TABLE
Date
Msg-id 22451.1303772621@sss.pgh.pa.us
Whole thread Raw
In response to Re: wrong hint message for ALTER FOREIGN TABLE  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: wrong hint message for ALTER FOREIGN TABLE  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> The sequence of steps that he posted wasn't actually right.

Yes, I did read the thread.

> The patch seems trivially correct,
> since this is obviously schizophrenic:

>           ereport(ERROR,
>                   (errcode(ERRCODE_WRONG_OBJECT_TYPE),
>                    errmsg("\"%s\" is not a foreign table",
> !                         RelationGetRelationName(targetrelation)),
> !                  errhint("Use ALTER FOREIGN TABLE instead.")));

Well, it's a pretty obvious global-search-and-replace error, but I fail
to see the advantage of just deleting the hint.  I was thinking

-             errhint("Use ALTER FOREIGN TABLE instead.")));
+             errhint("Use ALTER TABLE instead.")));

As per the other thread today, this advice would usually be correct,
so I think that not offering any advice at all would be a step down from
that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: branching for 9.2devel
Next
From: Tom Lane
Date:
Subject: Re: operator classes for index?