From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | Postgres Hackers List <hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] main tree is (slightly) damaged |
Date: | 1999-09-08 13:42:31 |
Message-ID: | 29852.936798151@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> 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.
Drat. I was really hoping that you'd just forgotten initdb --- the
parsetree changes I made a couple weeks ago could have explained this,
but not if you initdb'd.
The failure is presumably coming from an attempt to read a stored rule
or default-value clause that's not stored in the format that the read
procedures are expecting. I'm guessing that there is a node write proc
that's not the inverse of the corresponding node read proc, and you
happen to have a rule or default that has the right kind of node in it
to expose the bug.
Could you burrow in with a debugger and find out more about the rule or
default that's triggering the error?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 1999-09-08 14:41:36 | PG_UPGRADE status? |
Previous Message | Tom Lane | 1999-09-08 13:30:32 | Re: [HACKERS] Stability questions RE 6.5 and 6.3.2 & 6.3.2 problems |