Re: BUG #15654: COPY command not working for 2gb CSV files

From: sandy kumar <sandeep(dot)t(dot)kumar(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15654: COPY command not working for 2gb CSV files
Date: 2019-02-26 04:18:11
Message-ID: CACvO_JgLSD+82T1VXJGBmNx6BmrvUdR3Fwtt7edzpJ7cfvqDVg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks Michael and David for the information, is there any workaround for
this issue?

Thanks
Sandeep

On Tue, Feb 26, 2019 at 5:39 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> On Tue, Feb 26, 2019 at 12:52:58PM +1300, David Rowley wrote:
> > hmm, but we're talking about fstat() not stat(). Perhaps it suffers
> > from the same issue, but there does not appear to be a macro for
> > fstat() in win32_port.h therefore likely involves a less complex fix.
>
> I thought that was the case, and double-checking pgwin32_safestat()
> only maps to stat().
>
> Windows has the bad idea to declare _stat, and put the rest of the
> return results of the different calls of stat() and fstat() into
> different structures.
>
> Anyway, if I recall correctly, you are still going to run into issues
> if trying to map _stat64 to "struct stat". I have played with this
> problem for a couple of hours, and this did not finish well because of
> the define of stat to pgwin32_safestat in port.h. And we likely don't
> want to have a dedicated pg_stat struct in the full code tree as
> that's spread to a lot of places.
> --
> Michael
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-02-26 04:38:37 Re: BUG #15654: COPY command not working for 2gb CSV files
Previous Message Michael Paquier 2019-02-26 00:09:53 Re: BUG #15654: COPY command not working for 2gb CSV files