Re: File not found error on creating collation

On 20 September 2011 18:25, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thom Brown <thom(at)linux(dot)com> writes:
>> On 20 September 2011 17:45, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> BTW, on examining the code I note that we're doing something else that
>>> promotes the confusion of "bad locale name" with "bad file name": we're
>>> using errcode_for_file_access() to select the SQLSTATE.  If we don't
>>> believe that ENOENT should be taken at face value then this is pointless
>>> (none of the other spec-defined error codes for newlocale() are
>>> particularly sensible as file access errors).  I propose just reporting
>>> ERRCODE_INVALID_PARAMETER_VALUE instead.
>
>> *nods*
>
> OK, done.

Thanks.

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company