Jeff Ross <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster