| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Andreas 'ads' Scherbaum <ads(at)pgug(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Crash: invalid DSA memory alloc request |
| Date: | 2024-12-17 17:22:34 |
| Message-ID: | Z2GzWpr8_DmVC49R@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2024-12-17 17:36:24 | Re: SQL/JSON json_table plan clause |
| Previous Message | Melanie Plageman | 2024-12-17 17:06:28 | Re: Maybe we should reduce SKIP_PAGES_THRESHOLD a bit? |