Re: RES: Postgresql Crasching

On 1/25/19 10:50 AM, Márcio Antônio Sepp wrote:
>>
>> On 1/25/19 10:21 AM, Márcio Antônio Sepp wrote:
>>>
>>> Hi all,
>>>
>>>
>>> We are experiencing the follow error in last few weeks:
>>>
>>> Jan 25 16:03:51 FreeBSD11 kernel: pid 78639 (postgres), uid 770: exited
>> on
>>> signal 11 (core dumped)
>>> Jan 25 16:03:51 FreeBSD11 postgres[73403]: [7-1] 2019-01-25 16:03:51.135
>> -02
>>> [73403] WARNING: terminating connection because of crash of another
>> server
>>> process
>>> Jan 25 16:03:51 FreeBSD11 postgres[73403]: [7-2] 2019-01-25 16:03:51.135
>> -02
>>> [73403] DETAIL: The postmaster has commanded this server process to roll
>>> back the current transacti
>>> on and exit, because another server process exited abnormally and
>> possibly
>>> corrupted shared memory.
>>> Jan 25 16:03:51 FreeBSD11 postgres[73403]: [7-3] 2019-01-25 16:03:51.135
>> -02
>>> [73403] HINT: In a moment you should be able to reconnect to the
>> database
>>> and repeat your command.
>>
>> What is the logs just before the above?
>
>
> Jan 25 16:01:55 FreeBSD11 postgres[71605]: [6-2] 2019-01-25 16:01:55.733 -02 [71605] DETAIL: Key (tdoemp, codemp, codfil, origem, sercai, numdoc, tdopes, codpes, datpar)=(1, 59
> 84305, 1, 55, 1, 160, 1, 5984305000107, 201901) is not present in table "e026pag_p2019".
> Jan 25 16:01:55 FreeBSD11 postgres[71605]: [6-3] 2019-01-25 16:01:55.733 -02 [71605] STATEMENT: COMMIT
> Jan 25 16:02:35 FreeBSD11 postgres[73403]: [6-1] 2019-01-25 16:02:35.184 -02 [73403] ERROR: insert or update on table "e026par_p2019" violates foreign key constraint "e026par_p
> 2019_tdoemp_fkey"
> Jan 25 16:02:35 FreeBSD11 postgres[73403]: [6-2] 2019-01-25 16:02:35.184 -02 [73403] DETAIL: Key (tdoemp, codemp, codfil, origem, sercai, numdoc, tdopes, codpes, datpar)=(1, 59
> 84305, 1, 55, 1, 160, 1, 5984305000107, 201901) is not present in table "e026pag_p2019".
> Jan 25 16:02:35 FreeBSD11 postgres[73403]: [6-3] 2019-01-25 16:02:35.184 -02 [73403] STATEMENT: COMMIT
> Jan 25 16:03:51 FreeBSD11 kernel: pid 78639 (postgres), uid 770: exited on signal 11 (core dumped)
>

Hmm, a 1:16 between the query failing and the crash. Hard to say if
there is a cause and effect. I would follow Tom Lane's advice and see if
you can get a stack trace.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com