On Mon, 21 Sep 2009, Fabian Groffen wrote:
On 21-09-2009 06:09:08 -0700, Alex Bo. wrote:
I'm failing to restore a dump from Feb09 to Aug09. I get these errors continuously when I try to restore:
0 tuples !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK) !current transaction is aborted (please ROLLBACK)
The problem is that the error messages aren't descriptive, I can't know what's going on. Any ideas?
You can try mclient -e, which echoes out the statement before it is sending them to the server, which might give you a dialog of what's going on. It's a feature request (that I'm willing to consider to implement) to request a line number of file or standard input from mclient when it encounters an error.
The errors that are observed are probably due to the paralel loader quiting. And also gives a problem finding out what line breaks. Now the solution might be to disable(?) the paralel loader, or more easy: load it from a file and hope that the error message will show up. Stefan