On 01/22/2013 07:57 AM, Cliff de Carteret wrote:
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.
What is this local wal_archive directory?
From a previous post:
"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
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?
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
So what did you do to get the database running again?
--
Adrian Klaver
adrian.klaver@xxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
