Re: [Patch] Windows relation extension failure at 2GB and 4GB
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Bryan Green <dbryan.green@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, pgsql-hackers@lists.postgresql.org
Date: 2025-11-06T17:45:30Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Replace off_t by pgoff_t in I/O routines
- 84fb27511dbe 19 (unreleased) landed
-
Add check for large files in meson.build
- d715aaa76f68 16.12 landed
- f6c1342e72aa 17.8 landed
- 434b605745a1 18.2 landed
- 79cd66f28c65 19 (unreleased) landed
Hi, On 2025-11-06 11:17:52 -0600, Bryan Green wrote: > From d3f7543a35b3b72a7069188302cbfc7e4de9120b Mon Sep 17 00:00:00 2001 > From: Bryan Green <dbryan.green@gmail.com> > Date: Thu, 6 Nov 2025 10:56:02 -0600 > Subject: [PATCH] Fix Windows file I/O to support files larger than 2GB Could we add a testcase that actually exercises at least some of the codepaths? We presumably wouldn't want to actually write that much data, but it shouldn't be hard to write portable code to create a file with holes... Greetings, Andres Freund