Re: BUG #18334: Segfault when running a query with parallel workers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: mba(dot)ogolny(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18334: Segfault when running a query with parallel workers
Date: 2024-02-06 01:51:19
Message-ID: 316598.1707184279@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-02-06 02:18:14 Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue
Previous Message Michael Paquier 2024-02-06 01:32:25 Re: BUG #18333: Postgres is crashing if we have special character in the query