PokerTracker

I frequently have to start up PostGre SQL manually after my computer boots, even though I have it set up to load at boot up (at least I think so) . . . are there any settings/registry keys I can check or modify to make sure it's properly set up to load when Windows (XP Pro) boots?

when you run the services.msc snap-in, what is the properties showing for the postgres service regards "startup type"?

susan

keggler wrote:when you run the services.msc snap-in, what is the properties showing for the postgres service regards "startup type"?

It shows Startup Type "automatic" and Log On As ".\postgres", yet it continues NOT to start up automatically; is there a setting I can change in the services menu to fix this?

in the services snap-in, have you got a path to the executable that looks something like this:

"C:\Program Files\PostgreSQL\8.3\bin\pg_ctl.exe" runservice -w -N "pgsql-8.3" -D "C:\Program Files\PostgreSQL\8.3\data\"

also, is there anything in the Windows event log that might indicate the services starts at boot, then gets stopped [by something]?


susan

Ive having the same problem, in services, postgres is supposed to be starting automatically in startup...but it doesnt.
this problem has been occuring since my machine got dumped...
when i manually told it in start in that windows snapin thing, it said that the service 'started and then stopped'

A few things to check:

Run 'net user' from a command prompt. Do you see the postgres user there?

In the services snap-in:

Right click "PostgresSQL Database Sever ..."
Click Properties.
Click the Log On tab.

Check the following:
"This account:" selected and filled with ".\postgres"
Type and retype the password.

postgres is there
and it still wont let me run it...
how do i reinstall without losing my database?

Wildebeest wrote:how do i reinstall without losing my database?

I suggest you don't. You need to look in the System Log and find out why it won't start.

Wildebeest wrote:postgres is there
and it still wont let me run it...
how do i reinstall without losing my database?

you could always back your database up; and for good measure, make sure you have all the hh's backed up as well - then wack postgres and start a fresh with a new db, then restore or re-populate; but methinks the postgres service problem will persist even if you do that...

check the windows event log to see why it won't start and post back - it could be another app. with a lock on a folder on registry key that's inhibiting postgres from getting going...


susan

keggler wrote:in the services snap-in, have you got a path to the executable that looks something like this:

"C:\Program Files\PostgreSQL\8.3\bin\pg_ctl.exe" runservice -w -N "pgsql-8.3" -D "C:\Program Files\PostgreSQL\8.3\data\"

also, is there anything in the Windows event log that might indicate the services starts at boot, then gets stopped [by something]?

Yup, I do . . . after a few re-boots and paying closer attention, I'm now thinking PostGre is actually set up right, as it does start up about half the time . . . the other times, some other app must be interfering with it, but I haven't been able to figure out what might be the culprit. If I do figure that out, I'll update this post, as someone else might be having the same issue. . . .