The following bug has been logged online:
Bug reference: 2474
Logged by: Francisco Calm
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Solaris 5.9
Description: cp: cannot access ~/archivedir/00000001.history
Details:
I thought the history is of the format
â0000000100001234000055CD.007C9330.backupâ
-rw------- 1 postgres postgres 1201 Jun 8 15:32
postgresql-2006-06-08_153234.log
$ more postgresql-2006-06-08_153234.log
<2006-06-08 15:32:34 PDT>LOG: database system was shut down at 2006-06-08
15:18:50 PDT
<2006-06-08 15:32:34 PDT>LOG: starting archive recovery
<2006-06-08 15:32:34 PDT>LOG: restore_command = "cp
/tempfdas/db/postgres/archivedir/%f "%p""
cp: cannot access /tempfdas/db/postgres/archivedir/00000001.history
<2006-06-08 15:32:35 PDT>LOG: restored log file "000000010000000000000010"
from archive
<2006-06-08 15:32:35 PDT>LOG: checkpoint record is at 0/10A212F8
<2006-06-08 15:32:35 PDT>LOG: redo record is at 0/10A212F8; undo record is
at 0/0; shutdown TRUE
<2006-06-08 15:32:35 PDT>LOG: next transaction ID: 185441; next OID: 27048
<2006-06-08 15:32:35 PDT>LOG: next MultiXactId: 1; next MultiXactOffset: 0
<2006-06-08 15:32:35 PDT>LOG: automatic recovery in progress
<2006-06-08 15:32:35 PDT>LOG: record with zero length at 0/10A21348
<2006-06-08 15:32:35 PDT>LOG: redo is not required
<2006-06-08 15:32:35 PDT>LOG: restored log file "000000010000000000000010"
from archive
<2006-06-08 15:32:35 PDT>LOG: archive recovery complete
<2006-06-08 15:32:35 PDT>LOG: database system is ready
<2006-06-08 15:32:35 PDT>LOG: transaction ID wrap limit is 2147484146,
limited by database "postgres"
I was able to recover thou, but the subject (00000001.history) just keep on
bothering me.
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
