Re: FSM corruption and standby servers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Hunley, Douglas" <douglas(dot)hunley(at)openscg(dot)com>
Cc: Tim Goodaire <tgoodaire(at)dyn(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: FSM corruption and standby servers
Date: 2016-10-31 16:55:36
Message-ID: 20566.1477932936@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Hunley, Douglas" <douglas(dot)hunley(at)openscg(dot)com> writes:
> On Mon, Oct 31, 2016 at 10:38 AM, Tim Goodaire <tgoodaire(at)dyn(dot)com> wrote:
>> I have a question regarding the FSM corruption bug that is fixed in
>> postgresql 9.5.5 (https://wiki.postgresql.org/wiki/Free_Space_Map_Problems)
>> If I don't find any corruption on a master database, is it still possible
>> that there is corruption on the standbys?

> It shouldn't be, iirc. FSMs are only ever created/updated by vacuum, which
> doesn't run on a slave until it is promoted to a master.

The problem is that the WAL data can be wrong in these cases, and since
the standbys only know what they were told in the WAL stream, their images
will be wrong even if the master is valid.

I would have thought that the referenced page is clear enough about
needing to check the standbys; do you think it isn't?

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tim Goodaire 2016-10-31 17:19:12 Re: FSM corruption and standby servers
Previous Message Hunley, Douglas 2016-10-31 16:34:42 Re: FSM corruption and standby servers