pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hunley, Douglas <douglas.hunley@openscg.com>
Cc: Tim Goodaire <tgoodaire@dyn.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: FSM corruption and standby servers
Date: Mon, 31 Oct 2016 12:55:36 -0400
Message-ID: <20566.1477932936@sss.pgh.pa.us> (raw)
In-Reply-To: <CAAD=pwHsr-wi1-pvPp3GzBP+f+X3f_KD2TcvMU9rqGqrE6Tt+w@mail.gmail.com>
References: <CABP2sqKiPTUiXEoL1K2FD6dWwFpVNFHC_EhOzTca1miZkHaMsw@mail.gmail.com>
	<CAAD=pwHsr-wi1-pvPp3GzBP+f+X3f_KD2TcvMU9rqGqrE6Tt+w@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

"Hunley, Douglas" <douglas.hunley@openscg.com> writes:
> On Mon, Oct 31, 2016 at 10:38 AM, Tim Goodaire <tgoodaire@dyn.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


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (8+ messages)  latest in thread

Message-ID: <20566.1477932936@sss.pgh.pa.us>
Permalink:  ../20566.1477932936@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/20566.1477932936@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, douglas.hunley@openscg.com, tgoodaire@dyn.com
  Subject: Re: FSM corruption and standby servers
  In-Reply-To: <20566.1477932936@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox