From: | Marcin Barczyński <mba(dot)ogolny(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | mba(dot)ogolny(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18334: Segfault when running a query with parallel workers |
Date: | 2024-02-06 11:30:31 |
Message-ID: | CAP3o3PfuvuTO1CidONW1i5HYeJVei0QhSV5xdSTagTZ5A8BBiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Feb 6, 2024 at 2:51 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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.)
No, not really. This issue happens on a production machine and a large
volume of data (terabytes) is likely the cause of the error.
Regards,
Marcin Barczyński
From | Date | Subject | |
---|---|---|---|
Next Message | Karina Litskevich | 2024-02-06 12:58:09 | Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction |
Previous Message | Dave Cramer | 2024-02-06 10:45:46 | Re: BUG #18335: JDBC Postgress Kerberos authentication does'nt work without JAAS |