Hi Tom,
> > RTERangeTablePosn: RTE not found (internal error)
> Oh?
That's why I found at least; dunno wether this is directly related to
this, but judging depending on the time it occured, it's likely.
> > NOTICE: identifier "horse_exported_imported_by_year_country" will be
> > truncated to "horse_exported_imported_by_year"
> > Can this cause any error as listed above?
> No, I don't think so. Can you post a self-contained example for someone
> else to try? I'm still suspicious of flaky hardware, but ...
Another thing: the name of the view, to which the new name gets truncated,
already existed before. But no error message appears that the given view
used. Just the "NOTICE" of above gets displayed.
I am trying to assemble a self-contained example to show the error,
however it can take quite a while, cause except for this error, postgres
runs fine. Seems to appear only when lots of relation exist. I'll let the
list know as soon as I got a ready-to-run test suite.
Kind regards
... Ralph ...
