| From: | "Hunley, Douglas" <douglas(dot)hunley(at)openscg(dot)com> |
|---|---|
| To: | Tim Goodaire <tgoodaire(at)dyn(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: FSM corruption and standby servers |
| Date: | 2016-10-31 16:34:42 |
| Message-ID: | CAAD=pwHsr-wi1-pvPp3GzBP+f+X3f_KD2TcvMU9rqGqrE6Tt+w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
--
{
"name" : "douglas j hunley",
"email" : "douglas(dot)hunley(at)openscg(dot)com <doug(dot)hunley(at)gmail(dot)com>",
"title" : "database engineer",
"phone" : "+1 732 339 3419 x163"
}
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-10-31 16:55:36 | Re: FSM corruption and standby servers |
| Previous Message | Hunley, Douglas | 2016-10-31 16:26:23 | Re: WARNING: out of shared memory |