er, shedloads of this....
read(0, "", 4096) = 0 read(0, "", 4096) = 0 read(0, "", 4096) = 0 read(0, "", 4096) = 0 read(0, "", 4096) = 0 read(0, "", 4096) = 0 read(0, "", 4096) = 0 read(0, "", 4096) = 0 read(0, "", 4096) = 0 read(0, "", 4096) = 0 read(0, "", 4096) = 0
methinks thats not a good sign?
Shane
Gaetano Mendola wrote:
Shane Wright wrote:
Hi,
I'm trying to upgrade our 25Gb database from 7.1.3 to 7.3.4 - pg_dump worked fine, although piping through split to get a set of 1Gb files.
But, after a few attempts on using pg_restore to get the data into the new installation I'm having a few problems; basically it restores the first few tables fine (big tables too), but now it's just hanging on one table; using 100% CPU but hardly touching the disk at all (vmstat reports about 50kb every few minutes).
what show an strace on that process ?
Regards Gaetano Mendola
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
