Re: BUG #18334: Segfault when running a query with parallel workers - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18334: Segfault when running a query with parallel workers
Date
Msg-id 316598.1707184279@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18334: Segfault when running a query with parallel workers  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18334: Segfault when running a query with parallel workers  (Marcin Barczyński <mba.ogolny@gmail.com>)
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> Log messages:

> 2024-02-03 09:16:33.798 EST [3261686-102] app= LOG:  background worker
> "parallel worker" (PID 2387431) was terminated by signal 11: Segmentation
> fault
> 2024-02-03 09:16:33.798 EST [3261686-103] app= DETAIL:  Failed process was
> running: set max_parallel_workers=8; set work_mem='20GB'; 

It's hard to do anything with just the query.  Can you put together a
self-contained test case, including table definitions and some sample
data?  (The data most likely could be dummy generated data.)
It would also be useful to know what non-default settings you are
using.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #18333: Postgres is crashing if we have special character in the query
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue