Yes, we are copying from pg_xlog. By doing so we let the WAL-segments fill up (not using timeout) and we are able to recover within a 10 minute interval.
Could it be that this copy operation is causing the problem? Per -----Original Message----- From: Magnus Hagander [mailto:[EMAIL PROTECTED] Sent: 3. juni 2008 15:47 To: Per Lauvås Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Failing to recover after panic shutdown Per Lauvås wrote: > Hi > > I am running Postgres 8.2 on Windows 2003 server SP2. > > Every now and then (2-3 times a year) our Postgres service is down > and we need to manually start it. This is what we find: > > In log when going down: > 2008-06-02 13:40:02 PANIC: could not open file > "pg_xlog/000000010000001C00000081" (log file 28, segment 129): > Invalid argument Are you by any chance running an antivirus or other "security software" on this server? > We are archiving WAL-segments at a remote machine, and we are copying > non-filled WAL-segments every 10 minutes to be able to rebuild the DB > with a maximum of 10 minutes of missing data. (I don't know if that > has anything to do with it). How are you copying these files? Are you saying you're actually copying the files out of the pg_xlog directory, or are you using the archive_command along with archive_timeout? //Magnus -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
