The local wal_archive directory is a directory named "wal_archive" which is at the same file system level as the data directory. The time stamp states that it has not been used for several years so it looks to be redundant.
To get the database running again I moved an old postgres installation to a backups folder which gave me ~2G of space to start up again until I was able to mount a new disk and move the pg_xlog to a separate partition using a symbolic link.
On 22 January 2013 16:15, Adrian Klaver <adrian.klaver@xxxxxxxxx> wrote:
On 01/22/2013 07:57 AM, Cliff de Carteret wrote:What is this local wal_archive directory?
There are no files in the pg_xlog directory from before the database
crash except one file which ends in .backup, there are 759 files. In the
pg_xlog/archive_status folder there are 755 files.
The local ../wal_archive folder has no files in it at all whereas the
remote wal_archive folder has 147 files present.
>From a previous post:I see only /opt/postgres/remote_pgsql/wal_archive which I assumed was the remote. I am not sure where the local one fits in?
"LOG: archive command failed with exit code 1
DETAIL: The failed archive command was: test ! -f /opt/postgres/remote_pgsql/wal_archive/00000001000000A800000078 && cp pg_xlog/00000001000000A800000078 /opt/postgres/remote_pgsql/wal_archive/00000001000000A800000078
So what did you do to get the database running again?
The remote archive folder is not full and has ~14G whereas the local
archive folder was previously full but now it has been moved so it has 100G+
The archive directory is a mount and as the user postgres I can copy a
file into it successfully.
The current setup has been working successfully for several years until
the recent database crash
--
Adrian Klaver
adrian.klaver@xxxxxxxxx
