Magnus,
Thanks for the advice. I checked the Windows Event Logs and did not see
anything there meaningful. The pg_log had only one interesting msg
"incomplete startup packet" in one of the logs a couple days before Computer
A had powered down. I don't know what this log msg means but I assume it is
not the cause. But I'm neither a database expert or a Windows expert so I
could be wrong.
Thanks,
Dirk
----- Original Message -----
From: "Magnus Hagander" <mha@xxxxxxxxxxxxxx>
To: "Dirk Kalp" <dkalp@xxxxxxxxxxxxxx>; <pgsql-admin@xxxxxxxxxxxxxx>
Sent: Wednesday, August 10, 2005 3:23 PM
Subject: RE: [ADMIN] Trouble Getting Database Server Started
I see from the Postgres archives that one can simply take a
copy of the installed PostgreSQL directory folder and move it
in place of the PostsgreSQL folder on a working system. I
took another computer (Computer B) and ran the same
installation script and tested to verify I could connect with
psql. Window's Task Manager showed
6 postgres processes: postmaster.exe, pg_ctl.exe, and 4
postgres.exe. (Not sure what the 4 postgres.exe are for.)
That's normal. It's one logger, one bgwriter and two stats processes.
I don't know what caused Computer A to power down. It is in a
lab and someone may have inadvertently cut the power. Would
that corrupt the database to the point where I can't connect
to it or its startup mechanism be disrupted? I don't know
what role those 4 postgres.exe processes fill - are they part
of standard postgres startup? Secondly, I don't know why
sliding in the archived PostgreSQL folder on Computer B did not work.
It normally sholdn't. You'll need to look into your logs to see wha
thave happened. Both the files in pg_log and in the system eventlog.
//Magnus
