Re: BUG #15858: could not stat file - over 4GB

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Emil Iggland <emil(at)iggland(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15858: could not stat file - over 4GB
Date: 2020-10-12 12:33:32
Message-ID: CAC+AXB25aAHGzmrvKd97jQK3wjYHzbhb72wpvGym6OmFqpj5Sw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Mon, Oct 12, 2020 at 5:27 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Michael Paquier <michael(at)paquier(dot)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.

Regards,

Juan José Santamaría Flecha

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-10-12 13:32:13 BUG #16666: Slight memory leak when running pg_ctl reload
Previous Message Pavel Borisov 2020-10-12 12:30:02 Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2020-10-12 13:47:33 Re: partition routing layering in nodeModifyTable.c
Previous Message Andy Fan 2020-10-12 12:22:45 Re: [HACKERS] Runtime Partition Pruning