Re: postgres MultiXact 9.3 corruption resolved but advice needed - Mailing list pgsql-general

From Yvonne Murphy
Subject Re: postgres MultiXact 9.3 corruption resolved but advice needed
Date
Msg-id C180F266-880F-4CA2-8CCB-EA68A59A6BD4@vmware.com
Whole thread Raw
In response to Re: postgres MultiXact 9.3 corruption resolved but advice needed  (Eduardo Morras <emorrasg@yahoo.es>)
List pgsql-general
Thank you kindly for your reply,

I've read that the wraparound has to do with the amount of files in pg_multicast/members. So once the wraparound error
happensonce will it keep recurring  until we upgrade even though we've truncated most of the database,  

If we exported the db dropped it and then recreated it. It would create a new data directory with a small members
directory.Would this give us some breathing space until we hit the corruption again 

Thanks


> On 15 Oct 2016, at 20:51, Eduardo Morras <emorrasg@yahoo.es> wrote:
>
> On Sat, 15 Oct 2016 18:40:39 +0000
> Yvonne Murphy <ymurphy@vmware.com> wrote:
>
>> Our application runs against postgres 9.3.9.0-2921310. We recently
>> run into the dreaded ERROR:  MultiXactId 82578299 has not been
>> created yet -- apparent wraparound. We've truncated this big table.
>> Will truncating save us from getting this error soon again or does
>> this bug have nothing to do with the size of the table? The
>> application has also been tested against. 9.3.12 will upgrading to
>> this reduce the chance of us hitting the bug until we can get the
>> application tested in 9.5. thanks
>>
>
> It's fixed in 9.3.14
>
>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.postgresql.org_docs_9.3_static_release-2D9-2D3-2D14.html&d=CwIFAw&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=mQbITS1ux9CYPN1J1RXbOOYEuEJg6BkweZRAn9BwVv0&m=bqw1YuI4zfakqEw_shsiP35FhKFhlNHoDSuR_pY1vsg&s=kyUpHJqEVfkQd7AWGZDzAAJX8Z2kf2b6dzw9MWA8f3s&e=

>
> Prevent possible failure when vacuuming multixact IDs in an
> installation that has been pg_upgrade'd from pre-9.3 (Andrew Gierth,
> Álvaro Herrera)
> The usual symptom of this bug is errors like "MultiXactId NNN has not
> been created yet -- apparent wraparound".
>
>
> ---   ---
> Eduardo Morras <emorrasg@yahoo.es>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
>
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.postgresql.org_mailpref_pgsql-2Dgeneral&d=CwIFAw&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=mQbITS1ux9CYPN1J1RXbOOYEuEJg6BkweZRAn9BwVv0&m=bqw1YuI4zfakqEw_shsiP35FhKFhlNHoDSuR_pY1vsg&s=B5lKCS9L9zbC5YzBmnXVfM8AtXqYF4K0i-zg-E8ADoQ&e=



pgsql-general by date:

Previous
From: Antonio Silva
Date:
Subject: Re: could not connect to server
Next
From: Andreas Seltenreich
Date:
Subject: Re: Query generator