Re: Standby corruption after master is restarted

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: emre(at)hasegeli(dot)com, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Cc: gurkan(dot)gur(at)innogames(dot)com, david(dot)pusch(at)innogames(dot)com, patrick(dot)schmidt(at)innogames(dot)com
Subject: Re: Standby corruption after master is restarted
Date: 2018-04-14 17:46:45
Message-ID: fd9cf19d-a291-ef14-fc7d-774380767c31@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-04-16 03:01:25 BUG #15156: The application server could not be contacted.
Previous Message Tomas Vondra 2018-04-14 17:38:49 Re: Standby corruption after master is restarted

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2018-04-14 19:32:35 Setting rpath on llvmjit.so?
Previous Message David Arnold 2018-04-14 17:42:14 Re: Proposal: Adding json logging