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

From Thomas Munro
Subject Re: BUG #18334: Segfault when running a query with parallel workers
Date
Msg-id CA+hUKGLnoVvU4v7--m0aDLhc+TNYjyf60aL1Y=SkRFWU-2qdzw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18334: Segfault when running a query with parallel workers  (Marcin Barczyński <mba.ogolny@gmail.com>)
List pgsql-bugs
On Wed, Feb 7, 2024 at 12:30 AM Marcin Barczyński <mba.ogolny@gmail.com> wrote:
> On Tue, Feb 6, 2024 at 2:51 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > PG Bug reporting form <noreply@postgresql.org> writes:
> > > 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.)
>
> No, not really. This issue happens on a production machine and a large
> volume of data (terabytes) is likely the cause of the error.

Hi,

Could you please show EXPLAIN ANALYZE for the query?  In gdb from that
core, can you please show "info proc mappings", and in frame 0 "print
*area", and in frame 1, "print *tuple" and "print *hashtable"?



pgsql-bugs by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: BUG #17828: postgres_fdw leaks file descriptors on error and aborts aborted transaction in lack of fds
Next
From: PG Bug reporting form
Date:
Subject: BUG #18337: Unable to write temp variables path