On Mon, 2007-12-10 at 22:43 -0600, Brett Neumeier wrote: > It seems that the recovery command always copies the source WAL file > (with a name like 00000001000000020000009C) to a file path > "pg_xlog/RECOVERYXLOG", which is fine. However, then when we abort > recovery, postgresql seems to expect that the most recent WAL log > should be in pg_xlog with its original filename, e.g., the 0....9C > filename from above. This allows the recovery to be restartable, which you'll want even if if you haven't realised it yet. > This seems broken -- if the WAL file should wind up in the pg_xlog > directory with the 0...9C name, why isn't postgresql copying it there? This part of the design specifically allows infinitely long recoveries. You can only delete WAL files prior to the last restartpoint. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
