Re: Cleaning up PREPARE query strings?

From: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Cleaning up PREPARE query strings?
Date: 2026-07-15 05:48:01
Message-ID: CAOzEurTYoinojY7a7GfJut3XsuR=26ZuF87SYzKV7RFcKMbvWA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Thu, Mar 5, 2026 at 6:33 AM Sami Imseih <samimseih(at)gmail(dot)com> wrote:
> Here it is as a v4

I applied v4 and got an assertion failure with the following script.
pg_stat_statements is in shared_preload_libraries.

=# CREATE EXTENSION pg_stat_statements;
=# CREATE TABLE t (a int);
=# SELECT 1\; PREPARE p AS SELECT a FROM t WHERE a > 1\; SELECT 2;
=# ALTER TABLE t ADD COLUMN b int;
=# EXECUTE p;
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
TRAP: failed Assert("query_len <= strlen(query)"), File:
"queryjumblefuncs.c", Line: 102

--
Best regards,
Shinya Kato
NTT OSS Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Hayato Kuroda (Fujitsu) 2026-07-15 05:02:30 RE: Parallel Apply