Re: BUG #18108: server process was terminated by signal 11: Segmentation fault

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: liuqi7850(at)126(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18108: server process was terminated by signal 11: Segmentation fault
Date: 2023-09-14 11:49:34
Message-ID: CAApHDvrDBOkTma2DrXDPctGfLB03xwH2Az9OfrmAf=dLvuvNeg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 14 Sept 2023 at 21:04, PG Bug reporting form
<noreply(at)postgresql(dot)org> 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Sanford 2023-09-14 13:27:03 Re: Segmentation Fault
Previous Message David Rowley 2023-09-14 11:42:08 Re: BUG #18109: enable_partitionwise_aggregate does not apply when inserting or updating