Re: [HACKERS] main tree is (slightly) damaged - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [HACKERS] main tree is (slightly) damaged
Date
Msg-id 37D5D196.1DA47710@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] main tree is (slightly) damaged  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] main tree is (slightly) damaged
Re: [HACKERS] main tree is (slightly) damaged
List pgsql-hackers
> > I've got trouble in a *clean* checkout of this morning's current tree.
> > Something in the system tables is not quite consistant:
> > postgres=> \d
> > ERROR:  nodeRead: Bad type 0
> Yipes.  Perhaps there is some platform-dependency in the md.c changes
> I committed a couple days ago.  I am not seeing any such problems,
> but that doesn't prove a lot.  How far back was the last version
> that worked on your system?
> > Do any other platforms run the tests without trouble?
> HPUX 9 here.  This is a big-endian box; maybe a byte ordering issue?

postgres=> select * from pg_tables;
ERROR:  nodeRead: Bad type 0

I still see a problem. Did a "make clean install; initdb", as well as
a clean checkout of the current source tree from cvsup.

Is anyone else running regression tests besides the Toms? Can someone
report success on a linux box? Don't know where the problems are
coming from...

I'm sure I ran the regression tests around the v6.5.1 release date,
but haven't been doing code development since then (working on docs
instead) so haven't been testing...
                    - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] Stability questions RE 6.5 and 6.3.2 & 6.3.2 problems
Next
From: "Hiroshi Inoue"
Date:
Subject: RE: [HACKERS] optimizer pruning problem