Re: Workaround for bug #4608? - Mailing list pgsql-novice
From | Robert Campbell |
---|---|
Subject | Re: Workaround for bug #4608? |
Date | |
Msg-id | b57c4e1c0904220950m5f1cbb85ub704e5f42cc9cffa@mail.gmail.com Whole thread Raw |
In response to | Re: Workaround for bug #4608? ("Obe, Regina" <robe.dnd@cityofboston.gov>) |
List | pgsql-novice |
Well, to make thing stranger I installed 8.4 on a different WinXP Pro SP3 machine outside the Novell network, no McAfee, etc. It installed absolutely fine. Looking at the data folder permissions, they are exactly the same as on the first machine: Administrators, postgres. So why these two exactly similar permissions configurations work differently on the two machines is anybody's guess. Why did I have to add my specific user account to the permissions of machine 1 for it to see the folder? Perhaps Novell tweaks the way Windows handles folder permissions? Anyway, I guess for the few people who run into this issue, the workaround is to add the specific user account that you log in with to the data folder's permissions, with Full Control, and run initdb manually as mentioned. It screws up the Start and Stop scripts that come with the install; instead just follow the command line suggestion initdb gives after completing. On Wed, Apr 22, 2009 at 6:07 PM, Obe, Regina <robe.dnd@cityofboston.gov> wrote: > Bruce, > I doubt a normal install would work but perhaps might be worth trying. > As I recall the situation at least in my case > I would explicitly add full permission with a bunch of accounts to the > folder and then when I reran the PostgreSQL install, the installer > insisted on removing most of those permissions including the postgres > account. > > So its almost like sometimes the installer shoots itself in the foot by > removing its own access to the folder so that it can't even install. But > why this happens only sometimes I have no clue. > > Like I said on all the servers here I tested all exhibit the same odd > behavior, but my windows xp box which is also on the same windows 2003 > domain network but uses a local postgres account doesn't run into this > issue. > > I've installed on lots of standalone windows servers even windows 2008 > without any issue. > > Thanks, > Regina > > -----Original Message----- > From: Bruce Momjian [mailto:bruce@momjian.us] > Sent: Wednesday, April 22, 2009 11:05 AM > To: Robert Campbell > Cc: Obe, Regina; pgsql-novice@postgresql.org > Subject: Re: [NOVICE] Workaround for bug #4608? > > Robert Campbell wrote: >> I found the problem: it's a permissions issue. >> >> The autogenerated data folder has the following permissions: >> >> Administrators (MY_COMPUTER_NAME\Administrators) >> postgres (MY_COMPUTER_NAME\postgres) >> >> Once I added my Novell user MY_COMPUTER_NAME\my_novell_username with >> Full Control I was able to run initdb on it okay. > > My guess is that a normal install would work fine now too. > > -- > Bruce Momjian <bruce@momjian.us> http://momjian.us > EnterpriseDB http://enterprisedb.com > > + If your life is a hard drive, Christ can be your backup. + > ----------------------------------------- > The substance of this message, including any attachments, may be > confidential, legally privileged and/or exempt from disclosure > pursuant to Massachusetts law. It is intended > solely for the addressee. If you received this in error, please > contact the sender and delete the material from any computer. >
pgsql-novice by date: