From: | "Peter Geoghegan" <peter(dot)geoghegan86(at)gmail(dot)com> |
---|---|
To: | "Paolo Saudin" <paolo(at)ecometer(dot)it> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: R: Debugging Pl/PgSQL functions with the debug contrib module |
Date: | 2008-04-09 13:21:33 |
Message-ID: | db471ace0804090621o45e572edqf6ab1f185fd4fba2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Paolo,
Oh yes, I see it now. It was necessary to re-initialise the database
in order for that to appear, which I have not done until now.
Now I have a new problem. When I attempt to install postgres 8.3.1
with postgres automatically creating its own user account, the
installer complains:
"Service 'PostgreSQL Database Server 8.3'(pgsql-8.3) failed to start.
Verify that you have sufficient priveleges to start system services."
This, despite the fact that 4 postgres.exe processes are now visible
in task manager, running as the just created postgres user. I believe
that the installer creates accounts with the ability to start
services, so this shouldn't be a problem. The account I run
PGinstaller is an administrative account.
This is a new user account, not one from a previous postgres install.
I deleted all the older ones in the well hidden "Local Users and
Groups" dialog.
What should I do to prevent this messagebox from appearing, which
forces me to roll back the installation?
Regards,
Peter
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-04-09 13:28:24 | Re: Cannot use a standalone backend to VACUUM in "postgres"" |
Previous Message | Richard Huxton | 2008-04-09 13:18:49 | Re: begin transaction locks out other connections |