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

From Juan José Santamaría Flecha
Subject Re: BUG #15858: could not stat file - over 4GB
Date
Msg-id CAC+AXB0j9pN4z5XxMbn6+kcE_QM+CErjfYp-vVz2rU4suU7u=g@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15858: could not stat file - over 4GB  (Michael Paquier <michael@paquier.xyz>)
Responses Re: BUG #15858: could not stat file - over 4GB
List pgsql-bugs
On Wed, Jun 19, 2019 at 3:26 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> Windows is known for having limitations in its former implementations
> of stat(), and the various _stat structures they use make actually
> that much harder from a compatibility point of view:
> https://www.postgresql.org/message-id/1803D792815FC24D871C00D17AE95905CF5099@g01jpexmbkw24
>

Going through this discussion it is not clear to me if there was a
consensus about the shape of an acceptable patch. Would something like
the attached be suitable?

Regards,

Juan José Santamaría Flecha

Attachment

pgsql-bugs by date:

Previous
From: Albrecht Scheidig
Date:
Subject: XSS Bug in Query View
Next
From: Andrew Gierth
Date:
Subject: Re: BUG #15855: Using 'nextval' inside INSERT RULE in case of bulk data insertion.