Nathan Bossart writes:
> FWIW something I am hearing about more often these days, and what I believe
> Maxim's patch is actually after, is the 1GB limit on row size. Even if
> each field doesn't exceed 1GB (which is what artifacts.md seems to
> demonstrate), heap_form_tuple() and friends can fail
On Fri, Nov 07, 2025 at 09:32:45PM -0500, Tom Lane wrote:
> Maxim Zibitsker writes:
>> PostgreSQL's MaxAllocSize limit prevents storing individual
>> variable-length character strings exceeding ~1GB, causing "invalid
>> memory alloc request size" errors during INSERT operations on tables
>> with l
On 8/11/25 3:15, Maxim Zibitsker wrote:
PostgreSQL's MaxAllocSize limit prevents storing individual variable-length character
strings exceeding ~1GB, causing "invalid memory alloc request size" errors
during INSERT operations on tables with large text columns. Example reproduction included
in
Maxim Zibitsker writes:
> PostgreSQL's MaxAllocSize limit prevents storing individual variable-length
> character strings exceeding ~1GB, causing "invalid memory alloc request size"
> errors during INSERT operations on tables with large text columns.
This is news to no one. We are not especial
PostgreSQL's MaxAllocSize limit prevents storing individual variable-length
character strings exceeding ~1GB, causing "invalid memory alloc request size"
errors during INSERT operations on tables with large text columns. Example
reproduction included in artifacts.md.
This limitation also affect
