From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Ross <jross(at)wykids(dot)org> |
Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: psql error while restoring database: unrecognized node type: 655 |
Date: | 2007-07-16 23:37:43 |
Message-ID: | 25018.1184629063@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jeff Ross <jross(at)wykids(dot)org> writes:
> Tom Lane wrote:
>> Hmm [ pokes around a bit... ] Do you perhaps have a higher debug
>> verbosity level on this machine than the others? I can't immediately
>> think of a reason why anything would be trying to print an untransformed
>> NULL constant, but it sort of looks like that's what's happening.
> It seems that was it. When I installed postgres on the new machine, I
> uncommented and enabled debug_print_parse, something I did not do on the
> others. Now the entire dump/restore process runs error free.
Hah. So it's just that _outValue has been missing that case (since the
beginning of time, looks like :-(). We don't dump raw parse trees often
enough for anyone to have noticed.
Will fix, thanks for the report.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bowlby | 2007-07-16 23:52:07 | Issues with PL/PGSQL function.. |
Previous Message | Jeff Ross | 2007-07-16 23:08:16 | Re: psql error while restoring database: unrecognized node type: 655 |