From: Tom Lane <tgl@sss.pgh.pa.us>
To: iwebcas@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18514: Encountering an error invalid DSA memory alloc
 request size 1811939328 when executing script
In-reply-to: <18514-6be1e93cca5436f9@postgresql.org>
References: <18514-6be1e93cca5436f9@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 17 Jun 2024 16:12:10 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3477010.1718655763.1@sss.pgh.pa.us>
Date: Mon, 17 Jun 2024 16:22:43 -0400
Message-ID: <3477011.1718655763@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3477011.1718655763%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> 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.

Could you submit a self-contained reproducer script for this?  The
query alone is not enough information; we'd have to guess at your
table definition and contents.  (Note that dummy data might be
enough to provoke it, so you can probably anonymize or remove
anything sensitive.)

> Could you please assist in understanding why the execution plan changes

Probably as a result of switching from custom to generic plan.
There's not anything exciting about that, but we would like to
get to the bottom of the DSA allocation failure.

			regards, tom lane