Re: Standby corruption after master is restarted - Mailing list pgsql-bugs

From Tomas Vondra
Subject Re: Standby corruption after master is restarted
Date
Msg-id fd9cf19d-a291-ef14-fc7d-774380767c31@2ndquadrant.com
Whole thread Raw
In response to Re: Standby corruption after master is restarted  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: Standby corruption after master is restarted  (Emre Hasegeli <emre@hasegeli.com>)
List pgsql-bugs
On 04/14/2018 07:38 PM, Tomas Vondra wrote:
> 
> How was it restarted, actually? I see you're mentioning OOM killer, so I
> guess "kill -9". What about the first report - was it the same case, or
> was it restarted "nicely" using pg_ctl?
> 

Also, which process gets killed by the OOM killer? A random backend,
walsender or some other process?

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-bugs by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Standby corruption after master is restarted
Next
From: PG Bug reporting form
Date:
Subject: BUG #15156: The application server could not be contacted.