It was far stupider than that. I had been playing around with a
couple of different data clusters before doing a complete reinstall of
PostgreSQL. I just realized I was trying to start a cluster that I
was no longer using and the postgres account didn't have appropriate
permissions for. It's one of those things where once you ask the
question, you realize that the answer is implicit in the question.
But a useful followup question is, how do I make this start itself
when Windows starts? The service is set up to run as postgres and
execute
"C:\Program Files\PostgreSQL\8.3\bin\pg_ctl.exe" runservice -w -N
"pgsql-8.3" -D "C:\Program Files\PostgreSQL\8.3\data\"
This *is* pointing to the right data cluster (which I'm able to start
successfully from the command line), but it's not starting
automatically (even though it's configured to) and when I try to start
it manually within the Component Services Manager, it generates the
following error:
Error 1069: The service did not start due to a logon failure.
Thanks,
Lee Hachadoorian
PhD Student, Geography
Program in Earth & Environmental Sciences
CUNY Graduate Center
On Wed, Mar 12, 2008 at 2:05 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> On Wed, Mar 12, 2008 at 10:49 AM, Lee Hachadoorian
> <lee.hachadoorian@gmail.com> wrote:
>
> > Last week I set up Postgres 8.3 on a WindowsXP machine. Had it up and
> > running and imported data. Now when I try to start the server (after
> > a machine restart) I get the message:
> >
> > ********************************************************************************************
> > pg_ctl: another server might be running; trying to start server anyway
> > PANIC: could not open control file "global/pg_control": Permission denied
>
> Or it could just be that you do already have another postmaster up and
> running already.
>