Re: Standby corruption after master is restarted

From: Andres Freund <andres(at)anarazel(dot)de>
To: Emre Hasegeli <emre(at)hasegeli(dot)com>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>, gurkan(dot)gur(at)innogames(dot)com
Subject: Re: Standby corruption after master is restarted
Date: 2017-08-24 19:07:28
Message-ID: 20170824190728.6c6xtgdsviueyshy@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Hi,

On 2017-08-24 16:50:59 +0200, Emre Hasegeli wrote:
> One of our standby servers on a testing environment at InnoGames broke
> today. The master and the other standby server is working fine. I
> noticed that it happened right after the master had restarted. It
> looks to me like the WAL file is corrupted. I wanted to check, if it
> can be a bug. These were on the log file:

To clarify: Is fsync=off used anywhere, and was this an OS level /
hardware level restart? And just on the master, not a standby?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Emre Hasegeli 2017-08-24 20:19:22 Re: Standby corruption after master is restarted
Previous Message Arthur Zakirov 2017-08-24 19:01:34 Re: TO_TSVECTOR acts differently with national charcters

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-08-24 19:32:04 Re: obsolete code in pg_upgrade
Previous Message Tom Lane 2017-08-24 18:24:40 Re: [PATCH] Push limit to sort through a subquery