Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M274039=pgsql-hackers-arkari@postgresql.org>)
 id 1YxBAi-0003Ua-C0
 for pgsql-hackers@arkaria.postgresql.org; Tue, 26 May 2015 09:29:16 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M274039=pgsql-hackers-arkari@postgresql.org>)
 id 1YxBAg-0002rB-VY
 for pgsql-hackers@arkaria.postgresql.org; Tue, 26 May 2015 09:29:15 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <paul@pscs.co.uk>) id 1YxBAf-0002os-29
 for pgsql-hackers@postgresql.org; Tue, 26 May 2015 09:29:13 +0000
Received: from mail.pscs.co.uk ([188.65.177.237])
 by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.84) (envelope-from <paul@pscs.co.uk>)
 id 1YxBAb-0001gH-Qi; Tue, 26 May 2015 09:29:12 +0000
Authentication-Results: mail.pscs.co.uk; spf=none; auth=pass (cram-md5)
 smtp.auth=paul
Received: from lmail.pscs.co.uk ([82.68.5.206]) by mail.pscs.co.uk
 ([188.65.177.237] running VPOP3) with ESMTP; Tue, 26 May 2015 10:28:54
 +0100
Authentication-Results: lmail.pscs.co.uk; spf=none; auth=pass
 (cram-md5) smtp.auth=paul
Received: from [192.168.66.101] ([192.168.66.101]) by lmail.pscs.co.uk
 ([192.168.66.70] running VPOP3) with ESMTP; Tue, 26 May 2015 10:28:44
 +0100
Message-ID: <55643CCB.6060207@pscs.co.uk>
Date: Tue, 26 May 2015 10:28:43 +0100
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101
 Thunderbird/31.7.0
MIME-Version: 1.0
To: Tatsuo Ishii <ishii@postgresql.org>
CC: pgsql-hackers@postgresql.org
Subject: Re: ERROR: MultiXactId xxxx has not been created yet
 -- apparent wraparound
References: <556439CF.7070109@pscs.co.uk>
 <20150526.182301.1136661173535358505.t-ishii@sraoss.co.jp>
In-Reply-To: <20150526.182301.1136661173535358505.t-ishii@sraoss.co.jp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V6.11 - Registered
X-Organisation: Paul Smith Computer Services
X-Authenticated-Sender: paul
X-Pg-Spam-Score: -2.6 (--)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org



On 26/05/2015 10:23, Tatsuo Ishii wrote:
> It was fixed in 9.3.7.

OK.

Do you know what the bug number was or what it was called (I've tried 
searching for it before posting, but found nothing which seemed to be 
the same problem as ours).

Do you know whether, if we upgrade to 9.3.7/8, it will fix the problem 
in the current database, or is the data damage 'permanent', so we'll 
need to restore from backup and somehow merge in the latest data?


 


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers