From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Postgres Hackers List <hackers(at)postgresql(dot)org> |
Subject: | main tree is (slightly) damaged |
Date: | 1999-09-03 14:48:30 |
Message-ID: | 37CFDFBE.264A4DFD@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
Also, I'm getting failures in regression tests:
constraints .. failed
>From a bunch of similar messages; related to above symptom?:
ERROR: nodeRead: Bad type 0
sanity_check .. failed
One extra message during first vacuum:
ERROR: nodeRead: Bad type 0
misc .. failed
Different ordering in output. Wonder why it changed?
select_views .. failed
ERROR: nodeRead: Bad type 0
rules .. failed
ERROR: nodeRead: Bad type 0
plpgsql .. failed
Formatting for rows has changed in psql? Or something with plpgsql has
changed the contents? I haven't tried tracking this down.
976c976
< slotname |roomno |slotlink
|backlink
---
> slotname | roomno| slotlink|backlink
Do any other platforms run the tests without trouble? Does anyone have
a guess at when and/or what broke?? I'm running on linux-2.0.36/RH5.2
using the as-shipped compiler.
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-09-03 14:59:06 | Re: [HACKERS] Postgres' lexer |
Previous Message | Tom Lane | 1999-09-03 14:46:48 | Re: [HACKERS] md.c is feeling much better now, thank you |