Re: Crash: invalid DSA memory alloc request - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Crash: invalid DSA memory alloc request
Date
Msg-id Z2GzWpr8_DmVC49R@nathan
Whole thread Raw
In response to Re: Crash: invalid DSA memory alloc request  (Andres Freund <andres@anarazel.de>)
Responses Re: Crash: invalid DSA memory alloc request
List pgsql-hackers
On Tue, Dec 17, 2024 at 10:53:07AM -0500, Andres Freund wrote:
> On 2024-12-17 16:50:45 +0900, Michael Paquier wrote:
>> I don't see a huge point in backpatching, FWIW.
> 
> I don't see why we wouldn't want to backpatch? The number of objects here
> isn't entirely unrealistic to reach with relations alone, and if you enable
> e.g. function execution stats it can reasonably reach higher numbers more
> quickly. And use DSA_ALLOC_HUGE in that place feels like a rather low risk
> change?

Agreed, this feels low-risk enough to back-patch to at least v15, where
statistics were moved to shared memory.  But I don't see a strong reason to
avoid back-patching it to all supported versions, either.

-- 
nathan



pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Maybe we should reduce SKIP_PAGES_THRESHOLD a bit?
Next
From: Andrew Dunstan
Date:
Subject: Re: SQL/JSON json_table plan clause