Skip site navigation (1) Skip section navigation (2)

Re: win32 pgsql not installable

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>,pgsql-hackers-win32(at)postgresql(dot)org,Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Subject: Re: win32 pgsql not installable
Date: 2004-07-28 07:38:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers-win32
Magnus Hagander wrote:
> >I know I'm going to go on some people's nerves, but it's necessary.
> >
> >With the current "run-as-non-admin" restriction the windows installer 
> >doesn't work, and it will probably be ridiculously difficult 
> >to make it 
> >work unless this restriction is redesigned.
> Not commenting on the other parts, but *huh*? The windows installer
> works just fine. It does require that you manually set up a non-admin
> account, but it certainly *works*...

And you have to tell the system that user can start a service.

> >I don't see any point in restricting postgres.exe (i.e. the 
> >single user 
> >non-communicating version) to non-superusers. Installations 
> >are usually 
> >executed with admin privileges (non-admins won't be able to create 
> >services), and currently it fails to initialize the cluster with that 
> >d***d message. Consequently, it rolls back the complete installation 
> >leaving me at point zero.
> The installer already takes care of this, and executes initdb with the
> permissions of the service account, not the installer account. 
> The installer should probably check for admin permissions before
> accepting the account, though.
> If this does not work for you, it's a bug in the installer, or an
> incorrectly set up service account.
> I'm no longer commenting on the other part of the discussion :-), but
> the workarounds are in place and working in the installer. Assuming you
> do the service install, otherwise you have to do it manually.

I have a machine with 256MB RAM and had a lot of popup failure error
messages while it was testing the shared buffer value during initdb, and
the initdb failed too.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-hackers-win32 by date

Next:From: Bruce MomjianDate: 2004-07-28 07:40:40
Subject: Re: win32 pgsql not installable
Previous:From: 帅猛Date: 2004-07-28 02:45:51
Subject: Re: initdb problem in Korean OS.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group