Re: BUG #18334: Segfault when running a query with parallel workers
От | Marcin Barczyński |
---|---|
Тема | Re: BUG #18334: Segfault when running a query with parallel workers |
Дата | |
Msg-id | CAP3o3PfuvuTO1CidONW1i5HYeJVei0QhSV5xdSTagTZ5A8BBiQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #18334: Segfault when running a query with parallel workers (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #18334: Segfault when running a query with parallel workers
|
Список | pgsql-bugs |
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: > > 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
В списке pgsql-bugs по дате отправления: