On 2019-Nov-04, Marcel Ruff wrote:
> Now I have upgraded to postgresql 12 and get a crash about once per day,
> unfortunately our midleware (Java via current JDBC) stops immediately on
> this and all users are offline.
>
> In pg_log/postgresql-2019-10-31.csv I find entries like:
>
> 2019-10-31 07:03:03.750 CET,,,1516,,5db5cfa5.5ec,19,,2019-10-27 18:11:01
> CET,,0,LOG,00000,"server process (PID 27439) was terminated by signal
> 11: Speicherzugriffsfehler","Failed proc
> ess was running: update Location set enmea=$1, guid=$2, latDeci=$3,
> lonDeci=$4, modifiedByLoginName=$5, poiObjectId=$6, timestamp=$7,
> TRACK_ID=$8 where LOCATION_ID=$9",,,,,,,,""
> How can I track down the problem?
The first you need to do is obtain a crash dump. This page may help:
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD#Getting_a_trace_from_a_reproducibly_crashing_backend
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services