| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | "Menon, Deepak (Deepak)" <menond(at)avaya(dot)com> |
| Cc: | "Sankar, Uma (Uma) **CTR**" <usankar(at)avaya(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [External]Re: Postgres Crash Issue |
| Date: | 2022-03-15 13:32:13 |
| Message-ID: | 20220315133213.GC10372@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 15, 2022 at 01:30:25PM +0000, Menon, Deepak (Deepak) wrote:
> Hi Depesz,
>
> Then what does this message mean ?
>
> 2022-03-11 08:58:42.956 UTC [17115] DETAIL: 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.
When someone issues pg_ctl -m immediate stop (which is the immediate
shutdown). pg basically shutd backends in their head. This, in turn,
means that all other have to exit to avoid shared memory corruption.
Sometimes such exit happens before pg_ctl will kill next backend,
sometimes not. So you sometimes can get such messages.
depesz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Menon, Deepak (Deepak) | 2022-03-15 13:38:04 | RE: [External]Re: Postgres Crash Issue |
| Previous Message | Menon, Deepak (Deepak) | 2022-03-15 13:30:25 | RE: [External]Re: Postgres Crash Issue |