Request a Demo
Home   >   mailing lists

Re: [Patch] Windows relation extension failure at 2GB and 4GB - Mailing list pgsql-hackers

From Bryan Green
Subject Re: [Patch] Windows relation extension failure at 2GB and 4GB
Date
Msg-id a7c983fc-4416-4777-a1ba-590fc06884c0@gmail.com
Whole thread Raw
In response to Re: [Patch] Windows relation extension failure at 2GB and 4GB  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [Patch] Windows relation extension failure at 2GB and 4GB
Re: [Patch] Windows relation extension failure at 2GB and 4GB
List pgsql-hackers
Tree view 
On 11/8/2025 3:40 AM, Michael Paquier wrote:
> On Fri, Nov 07, 2025 at 12:32:21PM +0900, Michael Paquier wrote:
>> On Fri, Nov 07, 2025 at 03:56:07PM +1300, Thomas Munro wrote:
>>> (It's signed per POSIX and on Windows so I assume you meant to write 2GB here.)
>>
>> Yes, right..
> 
> So, please find attached a patch that adds a check for large files in
> meson as we do now in ./configure, for a backpatch down to v16 (once
> the branch freeze is lifted next week of course). 
> 
> Thoughts?
> --
> Michael
I have attached v4 of the patch after correcting some whitespace errors
and a struct that didn't need the pgoff_t modification as requested by
Thomas.  I also have attached Michael's patch where both patches can be
found by cfbot for the commitfest.

-- 
Bryan Green
EDB: https://www.enterprisedb.com
Attachment

pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Trigger more frequent autovacuums of heavy insert tables
Next
From: Nathan Bossart
Date:
Subject: Re: Improve LWLock tranche name visibility across backends