There is nothing in the log file (in pg_log dir) with regard to this.
Should I set any particular parameter in the postgresql.conf file to log
information about a failed startup? I have not altered or uncommented
any lines in the "ERROR REPORTING AND LOGGING" section of the conf file.
Thanks again,
--Rob Adams
Lennin Caro wrote:
what error show the log file?
--- On Mon, 8/4/08, Greg Smith <gsmith@xxxxxxxxxxxxx> wrote:
From: Greg Smith <gsmith@xxxxxxxxxxxxx>
Subject: Re: [GENERAL] recovery via base + WAL replay failure
To: "Rob Adams" <robfadams@xxxxxxx>
Cc: "postgres general" <pgsql-general@xxxxxxxxxxxxxx>
Date: Monday, August 4, 2008, 5:58 PM
On Sun, 3 Aug 2008, Rob Adams wrote:
I made a base backup while the postgres was running
using the following batch
file:
psql -d test_database -U user_name -c "SELECT
pg_start_backup('test');"
What did you have archive_command set to? That needs to
dump the WAL
files generated while the backup is going on somewhere that
gets copied
over after the main copy is done, and you need the last of
them referenced
by the backup copied over before you can use that backup.
Steps (1) and
(5) of
http://www.postgresql.org/docs/current/static/continuous-archiving.html
are the hard parts here and I don't see that you're
addressing them so
far, and that will keep the copy from starting if all the
files aren't
there.
--
* Greg Smith gsmith@xxxxxxxxxxxxx http://www.gregsmith.com
Baltimore, MD
--
Sent via pgsql-general mailing list
(pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
