Re: MultiXact member wraparound protections are disabled

Your right we looked back in our old logs and we do see the messages there
as well. Still what I'm not getting is since we restarted the database
after SAN FC re-cable effort auto-vacuum is running on all the threads
continuous. I have never seen auto-vacuum using all the threads 24*7 on
this database. Any thoughts ?

On Thu, Oct 13, 2016 at 8:35 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:

> AnandKumar, Karthik wrote:
> > Thanks. We started seeing this error right after a SAN FC re-cable
> effort - so yes, that would make sense.
> > We’ll do a little more digging to see if the 0000 could have gotten
> removed.
> > If that’s an older file that we have in our filesystem backups, is it
> safe to restore from there?
>
> Sure, the files are immutable after they are completed. I worry that if
> the system removed it automatically, it would just remove it again,
> though. Shouldn't happen on 9.4.5, but it seems just too much of a
> coincidence that that file was removed.
>
> Changes such as FC recabling should not cause anything like this. I
> mean, why a pg_multixact file and not a table data file? Very fishy.
>
> I'd advise to verify your older logs at the time of restarts whether the
> "multixact protections are enabled" message has ever appeared, or it has
> always been "protections are disabled". Maybe you've had the problem
> for ages and just never noticed ...
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>