From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | iwebcas(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18514: Encountering an error invalid DSA memory alloc request size 1811939328 when executing script |
Date: | 2024-06-17 20:22:26 |
Message-ID: | CAKFQuwZ4XUhB1N=+QhLV3t1Qjpk0ZnDxW67d7EbKkEo2UtFKow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Jun 17, 2024 at 1:14 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18514
> Logged by: iwebcas
> Email address: iwebcas(at)gmail(dot)com
> PostgreSQL version: 16.3
> Operating system: Debian 8.3.0-6 (PostgreSQL 16.3)
> Description:
>
> Issue Report: Invalid DSA Memory Allocation Request Size
>
> Summary:
> Encountering an error invalid DSA memory alloc request size 1811939328 when
> executing a prepared statement after multiple runs. The error occurs due to
> a different execution plan being chosen on the 6th attempt.
> [...]
> Version on which the error is not reproduced: "PostgreSQL 16.2 (Debian
> 16.2-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6)
> 8.3.0, 64-bit"
>
If this is indeed a regression from 16.2 odds are good you will need to
work around the bug. Namely by ensuring that a generic plan for that query
is never chosen. See: plan_cache_mode
https://www.postgresql.org/docs/current/runtime-config-query.html#GUC-PLAN-CACHE-MODE
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-06-17 20:22:43 | Re: BUG #18514: Encountering an error invalid DSA memory alloc request size 1811939328 when executing script |
Previous Message | Tom Lane | 2024-06-17 20:17:46 | Re: BUG #18512: Backend memory leak when using command parameters after generating notifications |