Re: BUG #15858: could not stat file - over 4GB - Mailing list pgsql-hackers

From Tom Lane
Subject Re: BUG #15858: could not stat file - over 4GB
Date
Msg-id 3100396.1602515618@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15858: could not stat file - over 4GB  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
Responses Re: BUG #15858: could not stat file - over 4GB  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
=?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= <juanjo.santamaria@gmail.com> writes:
> On Mon, Oct 12, 2020 at 5:27 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Michael Paquier <michael@paquier.xyz> writes:
>>> Why are we forcing errno=ENOENT here?  Wouldn't it be correct to use
>>> _dosmaperr(GetLastError()) to get the correct errno?

>> Fair question.  Juan, was there some good reason not to look at
>> GetLastError() in this step?

> Uhm, a good question indeed, forcing errno serves no purpose there.

OK, changed.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Shinoda, Noriyoshi (PN Japan A&PS Delivery)"
Date:
Subject: RE: Resetting spilled txn statistics in pg_stat_replication
Next
From: Tom Lane
Date:
Subject: Bizarre coding in recovery target GUC management