Re: [Patch] Windows relation extension failure at 2GB and 4GB
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
Cc: Michael Paquier <michael@paquier.xyz>,
Bryan Green <dbryan.green@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-11-12T11:26:03Z
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
On Wed, Nov 12, 2025 at 11:55 PM Dagfinn Ilmari Mannsåker <ilmari@ilmari.org> wrote: > I just noticed that the check is for 2GB, but the error message says > 1GB. -Dsegsize only accepts integers here and it's expressed in GB, so only 1 will actually work. Presumably you could set a size up to 2GB - 1 block using -Dsegsize_blocks instead and it would work, but that's clearly documented as developer-only. I noticed that too and scratched my head for a moment, but I think Michael used a defensible cut-off and a defensible error message, they just disagree :-)