visibilitymap_clear()s in vacuumlazy.c aren't WAL logged

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: visibilitymap_clear()s in vacuumlazy.c aren't WAL logged
Date: 2016-07-16 01:23:22
Message-ID: 20160716012322.l7zstzk6llg3zruh@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

The $subject says it all. Am I missing something, or is that not ok?
Now, these branches should never be hit, but it surely isn't good that
the corruption will persist on a primary, after it's explicitly been
fixed on the standby.

Greetings,

Andres Freund

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-07-16 01:32:03 Re: Reviewing freeze map code
Previous Message Andres Freund 2016-07-16 01:08:13 Re: Reviewing freeze map code