Charles wrote:
> The following bug has been logged online:
>
> Bug reference: 5163
> Logged by: Charles
> Email address: cnicol@mediasensorcorp.com
> PostgreSQL version: 8.4.1
> Operating system: Vista Home Premium
> Description: Admin can't connect and won't use port 5432
> Details:
>
> The installer forced me to use port 5433.
If you had an older copy of PostgreSQL still installed and it was using
port 5432 already, the installer would pick the next available port.
> So how can I make it work with the correct port and start it?
Uninstall or disable whatever's using port 5432. Then edit
postgresql.conf and change the port setting from 5433 to 5432 and
restart the PostgreSQL service.
> Not sure why it created a new User account on my login screen called
> postgress either. Was that necessary?
Security. PostgreSQL is a "sealed server" where the user is absolutely
never meant to mess with the data directory at all. The user has no
reason to access the data directory or be able to access it. So
postgresql creates a separate user account for the postgresql server and
restricts access to the data directory to that account.
This also means that if a security hole is discovered in the postgresql
server and someone is able to exploit postgresql to run code on your
machine, they can only do the things that the restricted-priveleges
postgresql account lets them do. They shouldn't be able to install a
rootkit, drop a virus on the machine, etc.
Running services under specific user accounts is absolutely standard on
all operating systems, including Windows. Many Microsoft services run
under different user accounts too, such as the IIS web server, Exchange
mail server, and in fact many standard built-in services on a normal
Windows system.
What's odd is that you noticed the new user account. Is it showing up on
your login screen? Or did you only notice because you were asked for a
password? A service account shouldn't make any difference to your use of
the machine, and it already has lots of them when it's installed.
> Baffled. I am blaming MS and VISTA at this point.
Incorrectly so in this case, I'm afraid.
--
Craig Ringer
