Re: BUG #18108: server process was terminated by signal 11: Segmentation fault
От
David Rowley
Тема
Re: BUG #18108: server process was terminated by signal 11: Segmentation fault
Дата
Msg-id
CAApHDvrDBOkTma2DrXDPctGfLB03xwH2Az9OfrmAf=dLvuvNeg@mail.gmail.com
Ответ на
BUG #18108: server process was terminated by signal 11: Segmentation fault (PG Bug reporting form)
Список
Дерево обсуждения
BUG #18108: server process was terminated by signal 11: Segmentation fault PG Bug reporting form <noreply@postgresql.org>
Re: BUG #18108: server process was terminated by signal 11: Segmentation fault David Rowley <dgrowleyml@gmail.com>
Re: BUG #18108: server process was terminated by signal 11: Segmentation fault Jay <liuqi7850@126.com>
Re: BUG #18108: server process was terminated by signal 11: Segmentation fault David Rowley <dgrowleyml@gmail.com>
Re: BUG #18108: server process was terminated by signal 11: Segmentation fault Michael Paquier <michael@paquier.xyz>
On Thu, 14 Sept 2023 at 21:04, PG Bug reporting form wrote: > Recently I executed a merge SQL with over 1.5W rows inside PG15.2, which > caused the database to report a crash error and then terminated all database > sessions,but changing the merge to insert syntax worked fine, I'm trying to > understand where this is and if I need to change the settings. > Below are the DB and OS logs(ID or address data was changed to unreal): It would be very difficult for us to do anything based on the information you've supplied here. Are you able to get a stack trace (See [1]) or come up with a self-contained script to reproduce it? I'm also not sure how many rows 1.5W is. David [1] https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
В списке pgsql-bugs по дате отправления
От: David Rowley
Дата: