Re: BUG #18333: Postgres is crashing if we have special character in the query - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #18333: Postgres is crashing if we have special character in the query
Date
Msg-id ZcGMKdCN7D4UeB30@paquier.xyz
Whole thread Raw
In response to BUG #18333: Postgres is crashing if we have special character in the query  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18333: Postgres is crashing if we have special character in the query
List pgsql-bugs
On Mon, Feb 05, 2024 at 10:30:33AM +0000, PG Bug reporting form wrote:
> I have installed Postgres-14.10 and when executing the below query, the
> postgres crashes. but the same query work well with PostgreSQL-14-9.
> I have a crash dump, but not sure, how can I attach it here.
>
> 2024-02-05 06:08:53.936 GMT [1680576] LOG:  server process (PID 2627861) was
> terminated by signal 11: Segmentation fault
> 2024-02-05 06:08:53.936 GMT [1680576] DETAIL:  Failed process was running:
> SELECT DISTINCT badsql.id_code,badsql.id_nr FROM badsql LEFT OUTER JOIN
> newsql on badsql.id_nr = newsql.id_nr  and badsql.vk_ek%2=newsql.ku_vk_ek;

It is going to be hard to say what's wrong without more details, like
a backtrace, or even better a self-contained SQL sequence that makes a
problem reproducible.  14.11 is planned for this week, so you may want
to give it a try and double-check if your problem is going away:
https://www.postgresql.org/developer/roadmap/
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Arnd Baranowski
Date:
Subject: Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue
Next
From: Tom Lane
Date:
Subject: Re: BUG #18334: Segfault when running a query with parallel workers