Re: Server Crash

Поиск
Список
Период
Сортировка
От Anjul Tyagi
Тема Re: Server Crash
Дата
Msg-id emeb32e4c8-e6bb-477f-b672-a87d8fa43dc5@iboss01081
обсуждение исходный текст
Ответ на Re: Server Crash  (Sergei Kornilov <sk@zsrv.org>)
Ответы Re: Server Crash
Список pgsql-bugs
Дерево обсуждения
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>
To: "Anjul Tyagi" <anjul@ibosstech-us.com>; "pgsql-bugs@lists.postgresql.org" <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
 
 
Вложения

В списке pgsql-bugs по дате отправления: