Thanks to Tom Lane and to Jan-Benedict Glaw for suggesting
a RAM problem; this has now been confirmed.
I'm relieved that Postgresql does not have what would have
been a very fundamental problem. That's the first time I
find a "bug" which is actually a hardware fault. I guess
sometimes the computer is wrong after all.
Thanks for the excellent feedback!
In response to
pgsql-bugs by date
|Next:||From: pgsql-bugs||Date: 2002-02-20 01:20:33|
|Subject: Bug #597: ResultSet.next() throws NullPointerException|
|Previous:||From: pgsql-bugs||Date: 2002-02-19 22:36:11|
|Subject: Bug #596: bind to 127.0.0.1 in pgstat.c in secure server|