Re: pgwin32_open returning EINVAL
От | Tom Lane |
---|---|
Тема | Re: pgwin32_open returning EINVAL |
Дата | |
Msg-id | 19071.1196371545@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pgwin32_open returning EINVAL (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: pgwin32_open returning EINVAL
|
Список | pgsql-hackers |
Alvaro Herrera <alvherre@alvh.no-ip.org> writes: > Tom Lane wrote: >> (2) Do we have any live cases where we must know this? > Yes. This thread shows the problem: > http://archives.postgresql.org/pgsql-es-ayuda/2007-11/msg00354.php > Basically he is getting this error: > 2007-11-16 14:54:16 ERROR: could not open relation 1663/16403/16487: Invalid argument Well, since EINVAL is the default result from _dosmaperr, and none of the cases it represents are "expected", why don't we just remove all of the explicit mappings to EINVAL from doserrors[]? Then we will get the LOG message you need, and we won't have to increase the chattiness level for anything else. regards, tom lane
В списке pgsql-hackers по дате отправления: