Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not beencreated yet -- apparent wraparound - Mailing list pgsql-bugs

From Phil Hildebrand
Subject Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not beencreated yet -- apparent wraparound
Date
Msg-id CAKk9fdXNbwXb4uH2KDs+2bvdkAWTgU53_EqWxOTzJ5dOoFWTKQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not beencreated yet -- apparent wraparound  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Thanks!

On Wed, Jan 2, 2019 at 5:53 AM Michael Paquier <michael@paquier.xyz> wrote:
On Tue, Jan 01, 2019 at 12:13:05AM -0800, Phil Hildebrand wrote:
> That said, these are VMs running on ESX hosts with SSD, so it's
> certainly possible.  We'll check the hosts as well.

You may have been bitten by a recent bug on ESX side.  Looking around
there has been a release 2 months ago which fixes an issue with
similar symptoms:
https://docs.vmware.com/en/VMware-vSphere/6.5/rn/esxi650-201810002.html

I am referring to this one in particular:
"PR 2209189: Heavy I/Os issued to a snapshot virtual machine using the
SEsparse format might cause guest OS file system inconsistencies."

And in this case this could be referring to 4kB blocks written where
they should not.
--
Michael
--
Phil Hildebrand
Sr. DBE @ Moz
206.696.3413

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not beencreated yet -- apparent wraparound
Next
From: Alexey Bashtanov
Date:
Subject: Is temporary functions feature official/supported? Found some issueswith it.