pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Alexey Bashtanov <bashtanov@imap.cc>
To: Anjul Tyagi <anjul@ibosstech-us.com>
To: Sergei Kornilov <sk@zsrv.org>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Server Crash
Date: Thu, 28 Jun 2018 14:10:51 +0100
Message-ID: <53e106c6-1b6c-827e-7f32-1fedcaf8a524@imap.cc> (raw)
In-Reply-To: <emeb32e4c8-e6bb-477f-b672-a87d8fa43dc5@iboss01081>
References: <emc5980c28-9d53-4310-b7ef-a25d5418ae84@iboss01081>
<6514671530091875@web12g.yandex.ru>
<emeb32e4c8-e6bb-477f-b672-a87d8fa43dc5@iboss01081>
Hello Anjul,
The first line of the log looks relevant.
My only guess is a stored procedure written in an untrusted language may
send a backend signal 14.
Do you have any of these, like pl/perl?
Best,
Alex
On 27/06/18 11:58, Anjul Tyagi wrote:
> Hi Sergei,
>
> thanks for your response. We have already plan to upgrade the same in
> PG 10, but i am scared if we faced the same issue with upgraded
> version as well.
>
> Regards,
>
> Anjul *TYAGI*
>
> **
>
> *ü****Go Green*
>
>
> ------ Original Message ------
> From: "Sergei Kornilov" <sk@zsrv.org <mailto:sk@zsrv.org>>
> To: "Anjul Tyagi" <anjul@ibosstech-us.com
> <mailto:anjul@ibosstech-us.com>>; "pgsql-bugs@lists.postgresql.org"
> <pgsql-bugs@lists.postgresql.org <mailto:pgsql-bugs@lists.postgresql.org>>
> Sent: 27-06-2018 15:01:15
> Subject: Re: Server Crash
>
>> Hello
>>> 2018-06-21 13:43:29 EDT [22212]: [4-1] user=cmsuser,db=forte
>>> ,host=10.10.1.3,port=10.10.1.3(56601),id=5b2bdea5.56c4,line=4DETAIL:
>>> The postmaster has commanded this server process to roll back the
>>> current transaction and exit, because another server process exited
>>> abnormally and possibly corrupted shared memory.
>> This is just consequence of error. Similar message is reported by
>> every client connect process. Real error was before all of these
>> messages.
>>> Postgres - Postgres 9.1.13
>> You are using unsupported major version and even very old minor. Last
>> released 9.1 was 9.1.24 (Release Date: 2016-10-27). You missed bug
>> fixes for 2.5 years.
>> According versioning policy [1] bug fixing ceases for EOL versions.
>> I suggest upgrade to one of supported version. Postgresql 10 is good
>> choice.
>> If error still occurs on supported version - we need exact error
>> message from failed backend.
>> regards, Sergei
>> [1] https://www.postgresql.org/support/versioning/
view thread (17+ messages)
Message-ID: <53e106c6-1b6c-827e-7f32-1fedcaf8a524@imap.cc> Permalink: ../53e106c6-1b6c-827e-7f32-1fedcaf8a524@imap.cc/ Also on: postgresql.org/message-id/53e106c6-1b6c-827e-7f32-1fedcaf8a524@imap.cc ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-admin@postgresql.org Cc: bashtanov@imap.cc, anjul@ibosstech-us.com, sk@zsrv.org, pgsql-bugs@lists.postgresql.org Subject: Re: Server Crash In-Reply-To: <53e106c6-1b6c-827e-7f32-1fedcaf8a524@imap.cc> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox