----- Original Message -----
From: "Thomas Kellerer" <spam_eater@gmx.net>
To: <pgsql-hackers-win32@postgresql.org>
Sent: Thursday, July 01, 2004 5:35 PM
Subject: Re: [pgsql-hackers-win32] PgSQL not as Administrator - probs on w
>
>
> On 01.07.2004 16:33 Tom Lane wrote:
> > I do *not* wish to allow people to override the safety check. We
> > periodically get complaints from Unix users that they don't see why
> > they shouldn't be allowed to start the server as root; we have not
> > been swayed by those arguments and I do not propose to be swayed
> > by the Windows variant. Unsafe is unsafe.
>
> "When in Rome..."
>
> The problem is that Unix users are used to that concept. Even if I assume
that
> the usual user trying/using Postgres is more experienced then the average
> Windows user, this is still not the way things are done in Windows.
Especially
> with a desktop computer.
> I fully understand your point when it comes to production servers, but I'm
sure
> that a lot of people would like to try out Postgres on their desktop and
use PG
> as a desktop database. Those users could be easily be taken aback from
using PG
> in that case.
>
And You are very right.
This is a part from (private) discussion I had with one of the win
developers:
> The current initdb is broken with "execution of postgresql by user with
> administrative rights is not allowed". I think developers are going VERY
> overboard with security, by NOT allowing users WITH certain administrative
> rights to run postgres - as a feature.
>
> We can't assume that developers (such as Java webapp developers, who want
to
> run postgres in their dev environment) have the right to add another user
> account. Want to limit the success of native? Surefire way to do it.
>
> I am not in the community and don't want my first comment to be bitching,
> but maybe you can bring that up for me?
It seems that the 'linux' way 'scares' some win users :-(
Regards !
