Re: patch: improve "user mapping not found" error message
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Ian Lawrence Barwick <barwick@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-07-03T09:22:48Z
Lists: pgsql-hackers
On 23.06.23 09:45, Ian Lawrence Barwick wrote:
> if (!HeapTupleIsValid(tp))
> + {
> + ForeignServer *server = GetForeignServer(serverid);
> +
> ereport(ERROR,
> (errcode(ERRCODE_UNDEFINED_OBJECT),
> - errmsg("user mapping not found for \"%s\"",
> - MappingUserName(userid))));
> + errmsg("user mapping not found for user \"%s\", server \"%s\"",
> + MappingUserName(userid),
> + server->servername)));
> + }
What if the foreign server does not exist either? Then this would show
a "cache lookup failed" error message, which I think we should avoid.
There is existing logic for handling this in
get_object_address_usermapping().
Commits
-
Improve "user mapping not found" error message
- 7e5f51779961 17.0 landed