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

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, williamedwinallen(at)live(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: BUG #15858: could not stat file - over 4GB
Date: 2019-06-29 06:19:18
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs pgsql-hackers

On Sat, Jun 29, 2019 at 4:30 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Thanks. Could you attach this patch to the next commit fest? We had
> many complaints with the current limitations with large files (pg_dump
> syncs its result files, so that breaks on Windows actually if the dump
> is larger than 2GB..), and we are going to need to do something. I
> find that stuff rather hard to backpatch, but let's see.

Done. [1]


Juan José Santamaría Flecha


In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Manuel Rigger 2019-06-29 15:51:06 VACUUM FULL results in deadlock
Previous Message Amit Langote 2019-06-29 05:13:04 Re: BUG #15873: Attaching a partition fails because it sees deleted columns

Browse pgsql-hackers by date

  From Date Subject
Next Message Juanjo Santamaria Flecha 2019-06-29 06:21:37 Re: TM format can mix encodings in to_char()
Previous Message Jaime Casanova 2019-06-29 05:40:38 Re: errbacktrace