Re: File not found error on creating collation

Thom Brown <thom(at)linux(dot)com> writes:
> On 20 September 2011 05:20, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> Maybe something like this?
>>> HINT: The operating system was unable to find any locale data for the
>>> locale name you specified.

>> Hmm, that's not bad. We could probably even call it errdetail, since
>> it's not so much a hint as explaining what the SUS spec states that the
>> ENOENT error code means here.

> Sounds good to me. If this is to be the errdetail, does that mean
> you'd be keeping the original message in tact? The problem with the
> actual error message is that it might cause the user to think along
> the lines of "Am I supposed to put a fully qualified path in this
> parameter?".

[ shrug... ] And who's to say that that's wrong? We have no knowledge
of the OS's conventions for naming locales. There's a limit to how
friendly we can make this message without turning it into something
that's actively misleading for platforms we failed to consider.

regards, tom lane