Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 46741633458 for ; Wed, 30 Dec 2009 13:30:30 -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 63807-10 for ; Wed, 30 Dec 2009 17:30:18 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mail.postgresql.org (Postfix) with ESMTP id 471F663330F for ; Wed, 30 Dec 2009 13:30:17 -0400 (AST) Received: by ewy26 with SMTP id 26so9592837ewy.3 for ; Wed, 30 Dec 2009 09:30:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=7ONVxP12UsCHGSPF0ZR2B9LVNYaUTP5OSgYEgBqwVls=; b=BagAXJl6OX6gL3Htb5MymLlg3nNmsPr2JcGoKsDCisfMD8SiCiZuZ+ojnJnkFDqtAm wD7f9KFVAwp3w5mw2PlCcUKSuf3/qYCKJwzekl1Qj4QXQ3wzGfIPxplbgPoffgvdt2LV ha2MUqQnQEaqohFbDvkvHtyg+kFw0NzG4hykk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Jwy/BjsmYPbn5/cpwnYJDFResCZUfDsYRINKKN2m53H8Gao4IgHHEPw5dRP8VbQrTo qPDQuATf9PSJ9uwIjd6YnVtg2zJ52dpB9KgDuxFMVNTVH8jLwtKFzCEGYJYtuykVOoif H8SUG3qPACjWgzLUQyS3ysK0tVQVOeu18GTdo= Received: by 10.213.50.129 with SMTP id z1mr19436914ebf.33.1262194213870; Wed, 30 Dec 2009 09:30:13 -0800 (PST) Received: from ?192.168.0.100? ([89.47.83.116]) by mx.google.com with ESMTPS id 14sm9674934ewy.15.2009.12.30.09.30.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 30 Dec 2009 09:30:13 -0800 (PST) Message-ID: <4B3B8E69.8060601@gmail.com> Date: Wed, 30 Dec 2009 19:31:21 +0200 From: Aioanei Rares User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20091109) MIME-Version: 1.0 To: Greg Smith 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> <4B3B8D6C.7020605@2ndquadrant.com> In-Reply-To: <4B3B8D6C.7020605@2ndquadrant.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/10 X-Sequence-Number: 22 Greg Smith wrote: > 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. > It fails on two very different (hardware-wise) machine, both with Debian, and also on a Fedora 12 machine, different from the 1st two.