Re: [GENERAL] WAL Archiving under Windows

2006-10-31 Thread Tim Tassonis
Hi Tom Richard Huxton wrote: Tim Tassonis wrote: Hi Tom Tom Lane wrote: Tim Tassonis <[EMAIL PROTECTED]> writes: The strange thing is, even with loglevel debug5, I don't get any log message indicating that postgres is even trying to call the command. Then it isn't, because there are defini

Re: [GENERAL] WAL Archiving under Windows

2006-10-31 Thread Richard Huxton
Tim Tassonis wrote: Hi Tom Tom Lane wrote: Tim Tassonis <[EMAIL PROTECTED]> writes: The strange thing is, even with loglevel debug5, I don't get any log message indicating that postgres is even trying to call the command. Then it isn't, because there are definitely log messages, which were s

Re: [GENERAL] WAL Archiving under Windows

2006-10-31 Thread Tim Tassonis
Hi Tom Tom Lane wrote: Tim Tassonis <[EMAIL PROTECTED]> writes: The strange thing is, even with loglevel debug5, I don't get any log message indicating that postgres is even trying to call the command. Then it isn't, because there are definitely log messages, which were specifically put there

Re: [GENERAL] WAL Archiving under Windows

2006-10-31 Thread Richard Huxton
Tim Tassonis wrote: Hi Tom Richard Huxton wrote: Tim Tassonis wrote: Hi Tom Tom Lane wrote: Tim Tassonis <[EMAIL PROTECTED]> writes: The strange thing is, even with loglevel debug5, I don't get any log message indicating that postgres is even trying to call the command. Then it isn't, be

Re: [GENERAL] WAL Archiving under Windows

2006-10-31 Thread Tom Lane
Tim Tassonis <[EMAIL PROTECTED]> writes: > The strange thing is, even with loglevel debug5, I don't get any log > message indicating that postgres is even trying to call the command. Then it isn't, because there are definitely log messages, which were specifically put there for the purpose of rec

Re: [GENERAL] WAL Archiving under Windows

2006-10-31 Thread Tim Tassonis
Richard Huxton wrote: Tim Tassonis wrote: We use version 8.1.3 and the following archive_coomand: archive_command = 'copy %p d:\\backup\\logs\%f' ^^^ Could the lack of a double-backslash be causing the problem? Sorry, that was a problem on my quot

Re: [GENERAL] WAL Archiving under Windows

2006-10-30 Thread Taras Kopets
Hi!> archive_command = 'copy %p d:\\backup\\logs\\%f' I think you should try something like this:archive_command = 'copy %p d:/backup/logs/%f'(using single / instead of \\).In documentation it is said:restore_command = 'copy /mnt/server/archivedir/%f "%p"' # Windows So I think the same format of

Re: [GENERAL] WAL Archiving under Windows

2006-10-30 Thread Richard Huxton
Tim Tassonis wrote: We use version 8.1.3 and the following archive_coomand: archive_command = 'copy %p d:\\backup\\logs\%f' ^^^ Could the lack of a double-backslash be causing the problem? Sorry, that was a problem on my quoting. The config file re

Re: [GENERAL] WAL Archiving under Windows

2006-10-30 Thread Tim Tassonis
Richard Huxton wrote: Tim Tassonis wrote: Hi Has anybody got any expierience with PITR recovery under Windows. PostgreSQL just doesn't seem to copy the WAL Files to the acrive location. We have done the initial backup and the first wal file was copied, but after that, it seems to ignore the

Re: [GENERAL] WAL Archiving under Windows

2006-10-30 Thread Richard Huxton
Tim Tassonis wrote: Hi Has anybody got any expierience with PITR recovery under Windows. PostgreSQL just doesn't seem to copy the WAL Files to the acrive location. We have done the initial backup and the first wal file was copied, but after that, it seems to ignore the newer ones. We now have

[GENERAL] WAL Archiving under Windows

2006-10-30 Thread Tim Tassonis
Hi Has anybody got any expierience with PITR recovery under Windows. PostgreSQL just doesn't seem to copy the WAL Files to the acrive location. We have done the initial backup and the first wal file was copied, but after that, it seems to ignore the newer ones. We now have two more wal filex