Re: File not found error on creating collation - Mailing list pgsql-hackers

From Tom Lane
Subject Re: File not found error on creating collation
Date
Msg-id 10663.1316539559@sss.pgh.pa.us
Whole thread Raw
In response to Re: File not found error on creating collation  (Thom Brown <thom@linux.com>)
Responses Re: File not found error on creating collation
List pgsql-hackers
Thom Brown <thom@linux.com> writes:
> On 20 September 2011 17:45, Tom Lane <tgl@sss.pgh.pa.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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: unite recovery.conf and postgresql.conf
Next
From: Tom Lane
Date:
Subject: Re: unite recovery.conf and postgresql.conf