> >OK. It turns out that the problem there was that the installer > >(postgresql-8.0-beta2-dev3.msi) actually created a user > >account which WAS a member of "Power Users", because my "Power > >Users" group included the group "NT AUTHORITY\Authenticated > >Users" (according to the MS website [1], this is the default > >configuration for Windows XP and Windows 2k Professional, > >though NOT for Win2k Server or Win2003 Server). This setting > >means that ANY new local account is AUTOMATICALLY a power > >user. When I realised this I removed the "NT > >AUTHORITY\Authenticated Users" from the "Power Users" local > >group, and the installer ran perfectly.
Magnus Hagander wrote: > That is an interesting note. I've never seen "Power Users" contain > Authenticated Users on any system I've installed, but the > page certainly > claims it. > However, it makes no claim about Windows XP that I can see. Only about > Windows 2000, and it shows the difference for the server platform. The second link in my earlier email mentioned WinXP Professional, which is the same as Win2k Professional in this regard, so it is definitely still a current issue: http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/windows_security_differences.asp Probably most serious use of pg would be on a "Server" version of the OS, but there are probably a lot more boxes out there running "Professional", so I'd expect it to come up quite often all the same, especially (as for me) when people are first evaluating the software. Cheers Con ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
