SEO

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" <Christian.Rengstl@klinik.uni-regensburg.de>
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

On 7/14/06, Christian Rengstl
<Christian.Rengstl@klinik.uni-regensburg.de> wrote:
> 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

you deleted wal files out of pg_xlog from a running server? have a
recent backup?

merlin

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On Fri, Jul 14, 2006 at 03:22:43PM +0200, Christian Rengstl wrote:
> 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.

pg_resetxlog might get you out of your current woes. But yeah, that was
a pretty dumb thing to do. Got a backup?

Have a nice dat,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFEt7fHIB7bNG8LQkwRAmAWAJ4tOB9PztpdDUyjYxGYwd dp5VnilwCfY0kO
lbot1IYHS7dkvFuVTdSsN7o=
=JrK9
-----END PGP SIGNATURE-----