Heikki Linnakangas hlinn...@iki.fi writes:
That doesn't work on Windows. As long as a walsender is keeping the old
file open, the unlink() on it fails. You get an error like this in the
startup process:
FATAL: could not rename file pg_xlog/RECOVERYXLOG to
pg_xlog/0001000D:
Starting with 9.2, when a WAL segment is restored from the archive, it
is copied over any existing file in pg_xlog with the same name. This is
done in two steps: first the file is restored from archive to a
temporary file called RECOVERYXLOG, then the old file is deleted and the
temporary file
On 05.09.2012 14:28, Tom Lane wrote:
Heikki Linnakangashlinn...@iki.fi writes:
That doesn't work on Windows. As long as a walsender is keeping the old
file open, the unlink() on it fails. You get an error like this in the
startup process:
FATAL: could not rename file pg_xlog/RECOVERYXLOG to
On 05.09.2012 16:45, Heikki Linnakangas wrote:
On 05.09.2012 14:28, Tom Lane wrote:
Heikki Linnakangashlinn...@iki.fi writes:
That doesn't work on Windows. As long as a walsender is keeping the old
file open, the unlink() on it fails. You get an error like this in the
startup process:
FATAL:
