From: | "Per Lauvaas" <per(dot)lauvaas(at)mintra(dot)no> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #2235: Wal archiving problems |
Date: | 2006-02-03 12:38:24 |
Message-ID: | 20060203123824.20C74F0B02@svr2.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 2235
Logged by: Per Lauvaas
Email address: per(dot)lauvaas(at)mintra(dot)no
PostgreSQL version: 8.0.3
Operating system: Windows Server 2003 SE SP1
Description: Wal archiving problems
Details:
Hi
We are using wal archiving. The wal segments are stored at another
computer:
(in postgresql.conf)
archive_command = 'copy /Y "%p"
\\\\Nasvolume1\\Backups\\campus\\20051125_backup\\wal_archive\\"%f"'
This following error has occured twice in 2 months:
Log output:
2005-11-27 14:19:011592LOG: archived transaction log file
"0000000100000001000000D5"
...
2005-11-27 21:45:031580PANIC: could not open file
"D:/PostgreSQL/8.0/data/pg_xlog/0000000100000001000000D7" (log file 1,
segment 215): Invalid argument
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.
I don't know if this is a bug, but maybe you know. The wal archiving is
working well except for the to occurences.
Regards Per
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2006-02-03 13:28:23 | Re: BUG #2225: Backend crash -- BIG table |
Previous Message | Kresimir Tonkovic | 2006-02-03 12:02:00 | BUG #2234: terminated by signal 11 |