| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgwin32_open returning EINVAL |
| Date: | 2007-11-29 21:25:45 |
| Message-ID: | 19071.1196371545@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2007-11-29 22:01:11 | Re: Status report on 8.3 release |
| Previous Message | Alvaro Herrera | 2007-11-29 21:15:04 | Re: pgwin32_open returning EINVAL |