RE: [External]Re: Postgres Crash Issue - Mailing list pgsql-general

From Menon, Deepak (Deepak)
Subject RE: [External]Re: Postgres Crash Issue
Date
Msg-id CO1PR15MB502027E5C91F1E1677D374E8D8109@CO1PR15MB5020.namprd15.prod.outlook.com
Whole thread Raw
In response to Re: [External]Re: Postgres Crash Issue  (hubert depesz lubaczewski <depesz@depesz.com>)
List pgsql-general
Thanks Depesz. Is there anyway to check the source of the command as this HA setup is managed by using Patroni 

Deepak Menon| Avaya Managed Services-Delivery|+91 9899012875| menond@avaya.com
Leave Alert : 

-----Original Message-----
From: depesz@depesz.com <depesz@depesz.com> 
Sent: Tuesday, March 15, 2022 7:02 PM
To: Menon, Deepak (Deepak) <menond@avaya.com>
Cc: Sankar, Uma (Uma) **CTR** <usankar@avaya.com>; pgsql-general@postgresql.org
Subject: Re: [External]Re: Postgres Crash Issue

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
currenttransaction 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

pgsql-general by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: [External]Re: Postgres Crash Issue
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: [External]Re: Postgres Crash Issue