Re: BUG #16033: segmentation fault when runing update

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: miha(dot)vrhovnik(at)naviter(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16033: segmentation fault when runing update
Date: 2019-10-02 13:51:54
Message-ID: 32600.1570024314@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> We are launching a ne service and decided to test the new 12rc1
> It happens that from time to time the postgresql crashes with segmentation
> fault.

We're unlikely to be able to do anything about this without more
information. A self-contained test case would be ideal, otherwise
maybe you could get a stack trace from the crash?

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Miha Vrhovnik 2019-10-02 15:40:35 Re: BUG #16033: segmentation fault when runing update
Previous Message PG Bug reporting form 2019-10-02 12:04:42 BUG #16033: segmentation fault when runing update