| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Anjul Tyagi <anjul(at)ibosstech-us(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Server Crash |
| Date: | 2018-06-27 09:31:15 |
| Message-ID: | 6514671530091875@web12g.yandex.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mariel Cherkassky | 2018-06-27 10:02:51 | Re: Investigate postgres 9.6.3 repmgr lag 4.0.4 |
| Previous Message | Fabio Pardi | 2018-06-27 09:13:30 | Re: Server Crash |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anjul Tyagi | 2018-06-27 10:40:18 | Re: Server Crash |
| Previous Message | Fabio Pardi | 2018-06-27 09:13:30 | Re: Server Crash |