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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Emil Iggland <emil(at)iggland(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Juanjo Santamaria Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
Subject: Re: BUG #15858: could not stat file - over 4GB
Date: 2020-10-09 20:22:20
Message-ID: 2831747.1602274940@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Emil Iggland <emil(at)iggland(dot)com> writes:
> I tested the patch at hand, and it performs as expected. Files larger than 4GB can be imported.

Thanks for testing!

I'd been expecting one of our Windows-savvy committers to pick this up,
but since nothing has been happening, I took it on myself to push it.
I'll probably regret that :-(

I made a few cosmetic changes, mostly reorganizing comments in a way
that made more sense to me.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-10-10 02:38:45 BUG #16665: Segmentation fault
Previous Message Francisco Olarte 2020-10-09 17:05:48 Re: BUG #16664: Problem running django

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2020-10-09 20:25:02 Re: Possible NULL dereferencing null pointer (src/backend/executor/nodeIncrementalSort.c)
Previous Message John Naylor 2020-10-09 19:24:25 Re: [PATCH] ecpg: fix progname memory leak