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.