Hi list, well now i know why it doesn't work. As the copy command did not work for a while the wal-files where gathering like mad and, as a beginner, i thought in order to clean up some disk space i should delete them. Well, that was probably the most stupid thing to do, because now pgsql tries to copy non-existing wal-files back and forth, which, as you might imagine, does not work very well. Is there a way to reset pgsql regarding the wal files and to tell it to start all over again to make wal files? I tried to restart the server, but without success. Please help
Chris >>> "Christian Rengstl" <[EMAIL PROTECTED]> 14.07.06 14.29 Uhr >>> Hi list, with the following archive_command (on Windows) archive_command = 'copy %p c:\\Archiv\\DBArchiv\\%f' I constantly have entries like the following in my log file: 2006-07-14 14:26:59 LOG: archive command "copy pg_xlog\000000010000000200000037 c:\Archiv\DBArchiv\000000010000000200000037" failed: return code 1 2006-07-14 14:27:00 LOG: archive command "copy pg_xlog\000000010000000200000037 c:\Archiv\DBArchiv\000000010000000200000037" failed: return code 1 2006-07-14 14:27:01 LOG: archive command "copy pg_xlog\000000010000000200000037 c:\Archiv\DBArchiv\000000010000000200000037" failed: return code 1 2006-07-14 14:27:01 WARNING: transaction log file "000000010000000200000037" could not be archived: too many failures Thanks for any advice! Chris ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
