On Sun, 2003-09-07 at 16:46, Bruce Momjian wrote:
> Andrew Dunstan wrote:
> >
> > Is there any reason to keep separate pg_id and pg_encoding programs, or
> > should they be merged into a C version of initdb? AFAICS initdb is the
> > only thing that uses them.
>
> Yes, I assume they would go awa
Gaetano Mendola wrote:
Work as non-root is a good practice for windows user too, I'll not bet
for the future that on windows all users will be "super user";
you can choose to start a service like a non super user too, I'd like to
mantain the same policy on windows too.
We're talking about
"Andreas Pflug" <[EMAIL PROTECTED]> wrote:
> Bruce Momjian wrote:
>
> >>We'll also need to decide the Windows equivalent of the 'don't run as
> >>root' rule - or even if we want to enforce it at all, given that it
> >>appears to be very common practice on Windows to run all services as a
> >>us
Bruce Momjian wrote:
We'll also need to decide the Windows equivalent of the 'don't run as
root' rule - or even if we want to enforce it at all, given that it
appears to be very common practice on Windows to run all services as a
user with Administrator privileges.
I assume we will relax t
Andrew Dunstan wrote:
>
> Is there any reason to keep separate pg_id and pg_encoding programs, or
> should they be merged into a C version of initdb? AFAICS initdb is the
> only thing that uses them.
Yes, I assume they would go away with a C version.
> We'll also need to decide the Windows equ
Is there any reason to keep separate pg_id and pg_encoding programs, or
should they be merged into a C version of initdb? AFAICS initdb is the
only thing that uses them.
We'll also need to decide the Windows equivalent of the 'don't run as
root' rule - or even if we want to enforce it at all, g
