On Tue, Aug 22, 2006 at 10:19:38AM -0400, Tom Lane wrote:
> > It may be a good idea to put a elog(LOG) with the error code in the
> > failure path of AllocateFile.
>
> That seems like a plan to me. I had been thinking of making
> win32error.c itself log the conversions, but that would not provide any
> context information. AllocateFile could log the file name along with
> the code, which should be enough info to associate a particular log
> entry with the actual failure.
Would it be possible to get errcode_for_file_access() to report the
results of GetLastError() for windows, or would that roduce spurious
results. At DEBUG lavel maybe?
Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.