Re: File not found error on creating collation
| От | Thom Brown |
|---|---|
| Тема | Re: File not found error on creating collation |
| Дата | |
| Msg-id | CAA-aLv45G1E11=OM3d=Yvj0wRYioBzp+8ntnjxm-E+VvgasCmg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: File not found error on creating collation (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
On 20 September 2011 18:25, Tom Lane <tgl@sss.pgh.pa.us> wrote: > 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. Thanks. -- Thom Brown Twitter: @darkixion IRC (freenode): dark_ixion Registered Linux user: #516935 EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: