pg.ddx.io  pgsql-testers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Smith <greg@2ndquadrant.com>
To: Aioanei Rares <schaiba@gmail.com>
Cc: pgsql-testers@postgresql.org
Subject: Re: [Fwd: "pg_regress: initdb failed" with git tree]
Date: Wed, 30 Dec 2009 12:27:08 -0500
Message-ID: <4B3B8D6C.7020605@2ndquadrant.com> (raw)
In-Reply-To: <4B3B8536.401@gmail.com>
References: <4B3B612E.2080102@gmail.com>
	<4B3B7E62.7070809@2ndquadrant.com>
	<4B3B846E.2030307@gmail.com>
	<4B3B8477.6050209@2ndquadrant.com>
	<4B3B8536.401@gmail.com>

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




view thread (9+ messages)  latest in thread

Message-ID: <4B3B8D6C.7020605@2ndquadrant.com>
Permalink:  ../4B3B8D6C.7020605@2ndquadrant.com/
Also on:    postgresql.org/message-id/4B3B8D6C.7020605@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-testers@postgresql.org
  Cc: greg@2ndquadrant.com, schaiba@gmail.com
  Subject: Re: [Fwd: "pg_regress: initdb failed" with git tree]
  In-Reply-To: <4B3B8D6C.7020605@2ndquadrant.com>
  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>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox