"D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes: > 100Mb instead of 100Mb -->1000Mb. I tried mounting with and without the TCP > option and it seemed to act the same but it was better than before. Now it > doesn't crash but trying to load a large table hangs. It gets to a point > where it is calling semop over and over getting a 0 return. It does that 81 > times in 0.989004 seconds and then hangs in the PostgreSQL code. It must be > in some sort of busy loop because there are no further system calls after the > last semop return and the CPU usage continues to climb.
Very bizarre. Looks like the last page it read was block 104 (851968/8192) in file "/source/data/cert/base/16556/17063". Could you provide a formatted dump of that page? I'm partial to pg_filedump which you can get from http://sources.redhat.com/rhdb/tools.html. Use switches -f -i to get a reasonably complete dump. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
