Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 379FE632841 for ; Wed, 30 Dec 2009 13:27:45 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 63683-06 for ; Wed, 30 Dec 2009 17:27:34 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mail.postgresql.org (Postfix) with ESMTP id 8C0B36327B2 for ; Wed, 30 Dec 2009 13:27:34 -0400 (AST) Received: from [192.168.1.3] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0Mb5Gp-1Nefjk1aqh-00Kp9T; Wed, 30 Dec 2009 18:27:32 +0100 Message-ID: <4B3B8D6C.7020605@2ndquadrant.com> Date: Wed, 30 Dec 2009 12:27:08 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Aioanei Rares CC: pgsql-testers@postgresql.org Subject: Re: [Fwd: "pg_regress: initdb failed" with git tree] References: <4B3B612E.2080102@gmail.com> <4B3B7E62.7070809@2ndquadrant.com> <4B3B846E.2030307@gmail.com> <4B3B8477.6050209@2ndquadrant.com> <4B3B8536.401@gmail.com> In-Reply-To: <4B3B8536.401@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+ozFKvjvLbCjeadCMvpShv9XtMgTCNv5uo5G+ XhF57IOvSQ7hvZhR2DsNLxfxGeL3WkEBDYHxLujQrP96eGJGb0 tVPU6X2yHXCSzG5pEfx/6sU1bjyg2sc X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200912/9 X-Sequence-Number: 21 Aioanei Rares wrote: >>> pg_regress: initdb failed >>> Examine /home/arares/postgresql/src/test/regress/log/initdb.log for >>> the reason. So here's the problem line: initializing dependencies ... FATAL: compressed data is corrupt That's coming from pretty deep inside PostgreSQL. Large bits of data that get inserted are compressed into what the database calls TOAST relations. This error shows up when the database tries to decompress those TOAST bits back into the original bytes again. That should never fail. Possible causes here: 1) System hardware instability. Intermittent RAM can cause this. I'd run a pass of memtest86+ just to rule that out in this situation, just to keep from chasing after the wrong thing 2) Buggy underlying OS, driver, or system library, somehow corrupting data that's been written before or during when it gets read back again. 3) PostgreSQL bug. Basically the tree is to figure out if it's specific to your system, then if it's specific to everyone one running the same Debian version you are, and then if neither of those are the case it might be possible to trace this down as a PostgreSQL issue. Not sure if you have any alternate systems to test against. The main reason I wouldn't assume it's a PostgreSQL bug initially is just because there are so many entries in the PostgreSQL buildfarm running this same test all the time without any problems. I think you're running a newer OS and libraries than any of them so far though. -- Greg Smith 2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.com