My Deja!
Wow. I've never been asked for help so directly. :-) Sure, I can try
to help.
Quick question first if I may, though. Please describe your
configuration in as much detail as possible. For example, currently I
am running
* Windows XP Professional SP1a
and the output of the command
$ cygcheck -c cygipc cygrunsrv cygwin postgresql
yields
Cygwin Package Information
Package Version Status
cygipc 2.02-1 OK
cygrunsrv 0.97-1 OK
cygwin 1.5.6-1 OK
postgresql 7.4.1-3 OK
And as I am using PostgreSQL v7.4.1 and started from scratch using
Jason's README, my data (and PID file) is now in /var/postgresql/data.
Please note that if you are not running the latest versions of
cygipc/postgresql, I highly recommend upgrading if at all possible, as
CygIPC is now a proper package of Cygwin (ipc-daemon2 basically), no
longer requiring a separate install. CygIPC2 also properly cleans up
after itself on system shutdowns, removing its files. Of course, if you
currently are running anything earlier than PostgreSQL v7.4, you will
need to follow the usual procedure of pg_dump'ing your data and then
restoring it once you have upgraded PostgreSQL. And be sure to RE-read
Jason's README as the default location of PostgreSQL data has changed
(though it's not written in stone or anything).
Once you respond, I can try to give you specific instructions on how to
set things up so that, even in the case of power/system failure, where
PostgreSQL does not shutdown properly, you can be sure that on reboot,
your dbms comes up. It's really not that difficult. The hardest part
is getting the service dependencies right. Then it's just a matter of a
batch file and some basic FireDaemon settings.
My Deja wrote:
> I am posting this query in relation to these threads at
> groups.google.com search 'firedaemon group:comp.databases.postgresql.*'
>
> PostgreSQL 7.3.2 running as NT service under Windows XP not always
>
> and
>
> Leftover PID files.
>
> Whenever I have to force a reboot, PostgreSQL does not start until I
> remove the PID file.
>
> I have even acquired FireDaemon to help me deal with the problem, but I
> am finding the configuration for PostgreSQL troublesome.
>
> Can Frank Seesink help me?
>
> Regards
>
> My Deja
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
