> Hmm. Unless you have reason to think that your hardware is flaky,
> I dislike writing this off as "just a glitch". I think most likely
> you got bit by a bug somewhere. Still, if we can't reproduce it
> it's gonna be mighty hard to find.
>
> If you have the time and interest, it might be worth repeating the
> whole setup sequence starting from initdb. I'm speculating that
> installing PostGIS might have somehow left corruption in server memory
> that later manifested as the visible problem.
>
I'm going to have a lot riding on this project if it flies, so if you think
there might something lurking in the background, I'll wipe the database and
rebuild it and we'll see. The data load is all scripted anyway, so it
shouldn't take more than an hour or so. I'll let you know either way
tomorrow morning.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
No comments:
Post a Comment