Re: Avoid a possible null pointer (src/backend/utils/adt/pg_locale.c)
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Ranier Vilela <ranier.vf@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>, Jeff Davis <pgsql@j-davis.com>
Date: 2023-09-08T06:24:28Z
Lists: pgsql-hackers
Attachments
- pglocale-elogs-v2.patch (text/x-diff) patch v2
On Wed, Sep 06, 2023 at 07:57:03AM -0300, Ranier Vilela wrote: > I think no one objected. Looking closer, there is much more inconsistency in this file depending on the routine called. How about something like the v2 attached instead to provide more context in the error message about the function called? Let's say, when the provider is known, we could use: + elog(ERROR, "unsupported collprovider (%s): %c", + "pg_strncoll", locale->provider); And when the provider is not known, we could use: + elog(ERROR, "unsupported collprovider (%s)", "pg_myfunc"); @Jeff (added now in CC), the refactoring done in d87d548c seems to be at the origin of this confusion, because, before this commit, we never generated this specific error for all these APIs where the locale is undefined. What is your take here? -- Michael
Commits
-
Refactor error messages for unsupported providers in pg_locale.c
- 800d5bcb982b 16.1 landed
- b8f44a477945 17.0 landed