ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound after missused pg_resetxlogs

From: RADIX Alain - externe <alain-externe(dot)radix(at)edf(dot)fr>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound after missused pg_resetxlogs
Date: 2017-10-16 12:03:41
Message-ID: 0d0020c5e43749b68689e2bdde9ba99d@NOEINTPEXMU005.NEOPROD.EDF.FR
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I'm facing a problem with a PostgreSQL 9.6.2 reporting this error when selecting a table
ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound

The root cause is not a Postgres bug but a buggy person that used pg_resetxlogs obviously without reading or understanding the documentation.

I'm trying to extract data from the db to create a new one ;-)
But pg_dump logically end with the same error.

I've seen the row with t_max = 3268957 page_inspect, I might use it to extract row from the page, but this will not be quite easy.

Is there a way to change the t_max to a value that won't fire the error, with this row.

Could pg_filedump be used in this problem configuration.

As usual, xlogs where deleted even stored in a directory named pg_wal :( ( I made the change before 10 ) and xlogs reseted by the same person that commented the backup months ago.

Hopefully, this is not a production database :-D but the user want to start qualification of the new application version today .. no luck for him.

Any advice of how to extract data is welcome.

At least, there is something to learn, renaming pg_xlog to pg_wal won't stop everybody :-/

Regards.

Alain RADIX
Expert SGBD
EDF - DSP/CSP IT-DMA
Solutions Groupe EDF
Expertise Applicative
32 Avenue Pablo Picasso
92016 Nanterre
alain-externe(dot)radix(at)edf(dot)fr
Tél. : 01.78.66.66.83

BAL Générique : support-oracle-niveau3(at)edf(dot)fr<mailto:support-oracle-niveau3(at)edf(dot)fr>
BAL Générique : support-postgres-niveau3(at)edf(dot)fr<mailto:support-postgres-niveau3(at)edf(dot)fr>
URL de notre communauté : https://sissi.edf.fr/web/expertise-sgbd/

[cid:image002(dot)png(at)01D34687(dot)91D9DDA0]

Un geste simple pour l'environnement, n'imprimez ce message que si vous en avez l'utilité.

Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.

Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.

Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.
____________________________________________________

This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.

If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.

E-mail communication cannot be guaranteed to be timely secure, error or virus-free.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jehan-Guillaume de Rorthais 2017-10-16 12:10:25 Re: Determine state of cluster (HA)
Previous Message Ashutosh Bapat 2017-10-16 11:33:07 Re: Partition-wise join for join between (declaratively) partitioned tables