From: | Zeugswetter Andreas OSB sIT <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Charlie Savage <cfis(at)savagexi(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED |
Date: | 2008-10-15 09:49:52 |
Message-ID: | 6DAFE8F5425AB84DB3FCA4537D829A561CE07FC6A0@M0164.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> The user running initdb (or the postmaster) needs
> SeCreateGlobalPrivilege - which is something we cannot really start
Why not ? Doesn't the pg installer already tweak the permissions of the
installation user. On XP you can connect to session 0, so that is an alternative on XP.
> telling people they must have. My view is that we revert the change
> (well, replace it with something that looks less like a broken attempt
> to use the global namespace) and leave it at that. iirc, the use of
yea, removing the +18 is grotesque, since it moves the shmem into the private
session but gives it a very misleading name (Global\ --> Global/).
> the global namespace is there to ensure things work as they should
> under a non-console terminal services session - which is pretty rare
> and can usually be avoided.
Hm? non-console is the default for remote, and all you can get in Vista/2008 and up.
The reason it should be in the Global namespace is that shmem is one part of
detecting an existing postmaster. Especially in situations where the db is started
by hand, the protection against duplicate startup is important.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-10-15 09:59:15 | Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED |
Previous Message | Gregory Stark | 2008-10-15 08:22:50 | Re: Bogus attribute-number range checks in spi.c |