Re: PostgreSQL - unrecognized win32 error code: 38

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: ZhenHua Cai <zhhua(dot)cai(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: PostgreSQL - unrecognized win32 error code: 38
Date: 2019-11-20 05:36:07
Message-ID: CA+hUKGJRVavqRg4H=KYAE0RW_XaRsS=B5XLw0E-ib_C3X05aKA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Oct 30, 2019 at 12:13 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> On Tue, Oct 29, 2019 at 9:23 PM ZhenHua Cai <zhhua(dot)cai(at)gmail(dot)com> wrote:
> > No, it doesn't call any in-core code.
>
> I wondered if this could be coming from the new code in
> src/port/pg_p{read,write}.c. ERROR_HANDLE_EOF is a documented
> GetLastError() return value after ReadFile() fails[1], but only for
> asynchronous files. We are using that interface ("overlapped" IO,
> their name for asynchronous IO, but the same interface can also do
> synchronous IO and happens to support an offset like Unix's pread()),
> but we're not opening file handles with FILE_FLAG_OVERLAPPED so we
> have a plain old synchronous handle here.

> [1] https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-readfile

Hi,

With a little help we got to the bottom of this:

https://www.postgresql.org/message-id/flat/CAC%2BAXB0_zNFUH1BrRGKUkFxvq3SxsojroJN70iTUA1gUNn_gag%40mail.gmail.com#cb324760c6a142ec4ed6abefa8e68f18

It should be fixed in the next release. Thanks for the report!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Soukaina Lahchiouach 2019-11-20 07:22:28
Previous Message Michael Paquier 2019-11-20 03:59:30 Re: REINDEX VERBOSE unknown option