Обсуждение: New pginstaller beta
A new beta-release of the win32 gui installer has been uploaded to pgfoundry. Postgresql is the snapshot from 20040731, with the win32 versioning/icon patch added, as well as the initdb auth patch (in the patch queue). Changes since last beta includes: * PgAdmin shortcuts are now predictably created. * Startmenu shortcuts are added to start and stop the database (pg_ctl or service depending on install method) * Service is set for automatic start instead of manual * Default encoding is now UNICODE * There is a base feature with a base directory so the install root can be changed at one place * The Next button is now always activated and a popup is shown if the specified passwords don't match. Workaround the fact that the activation required the password field to be de-focused before it happened. * A warning is shown if a service is installed without running initdb when there is no database in the directory already. * The installer now verifies that the user specified has Log on as a service right, and optionally grants it. * The installer now verifies that the user specified is not an administrative user, and refuses to continue if it is. * The installer now optionally creates a user account (with an optional random password) for the service. Plus a few other minor things. This addresses many of the issues brought up since the last beta, but not all. Please see the trackers on pgfoundry.org/projects/pginstaller for status on the other items, or to add new items. If you are upgrading from the previous snapshot, you'll have to uninstall the old version first. You can do this from Add/Remove progrmas, or by running "msiexec /x postgresql-7.5-devel.msi" on the commandline. This will not remove the data directory. You can run the new version on the same data directory, but we'd appreciate testing of clean installations anyway. In that case, pg_dump/reload and manual removal of the data directory is needed. (Full testing would also require removal/recreation of the service account, of course). As before, please post your feedback to the mailinglist on pgfoundry.org, or use the trackers. And thanks for all the feedback on the first beta! //Magnus & Dave
It installed cleanly for me, and created the user too. The "initializing database" window was blank and took a long time. I think you need a message there, but all the other issues I raised were fixed. Thanks. This is BIG! --------------------------------------------------------------------------- Magnus Hagander wrote: > A new beta-release of the win32 gui installer has been uploaded to > pgfoundry. > > Postgresql is the snapshot from 20040731, with the win32 versioning/icon > patch added, as well as the initdb auth patch (in the patch queue). > > Changes since last beta includes: > * PgAdmin shortcuts are now predictably created. > * Startmenu shortcuts are added to start and stop the database (pg_ctl > or service depending on install method) > * Service is set for automatic start instead of manual > * Default encoding is now UNICODE > * There is a base feature with a base directory so the install root can > be changed at one place > * The Next button is now always activated and a popup is shown if the > specified passwords don't match. Workaround the fact that the activation > required the password field to be de-focused before it happened. > * A warning is shown if a service is installed without running initdb > when there is no database in the directory already. > * The installer now verifies that the user specified has Log on as a > service right, and optionally grants it. > * The installer now verifies that the user specified is not an > administrative user, and refuses to continue if it is. > * The installer now optionally creates a user account (with an optional > random password) for the service. > > > Plus a few other minor things. > > This addresses many of the issues brought up since the last beta, but > not all. Please see the trackers on pgfoundry.org/projects/pginstaller > for status on the other items, or to add new items. > > > If you are upgrading from the previous snapshot, you'll have to > uninstall the old version first. You can do this from Add/Remove > progrmas, or by running "msiexec /x postgresql-7.5-devel.msi" on the > commandline. This will not remove the data directory. > You can run the new version on the same data directory, but we'd > appreciate testing of clean installations anyway. In that case, > pg_dump/reload and manual removal of the data directory is needed. (Full > testing would also require removal/recreation of the service account, of > course). > > > As before, please post your feedback to the mailinglist on > pgfoundry.org, or use the trackers. > > And thanks for all the feedback on the first beta! > > //Magnus & Dave > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
Magnus Hagander wrote: > A new beta-release of the win32 gui installer has been uploaded to > pgfoundry. > > Postgresql is the snapshot from 20040731, with the win32 versioning/icon > patch added, as well as the initdb auth patch (in the patch queue). On Win2K SP4 I am getting an error during initdb: Failed to tun initdb: 1! Please see the logfile in 'C:\Program Files\PostgreSQL\7.5\tmp\initdb.log'. That log file contains: The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale C. fixing permissions on existing directory C:/Program Files/PostgreSQL/7.5/data ... ok creating directory C:/Program Files/PostgreSQL/7.5/data/global ... Access is denied. initdb: failed initdb: removing contents of data directory "C:/Program Files/PostgreSQL/7.5/data" initdb: failed I am running this while logged in on a domain account that has both local and domain admin priviledges. I have created the user "postgres" and granted it "Log in as a service" priviledges. Permissions on the C:/Program Files/PostgreSQL/7.5/data/ dir are set by the installer in such a way that the postgres user has Change, and the rest has nothing. From the error it appears that initdb was running as 'me' instead of 'postgres'. Is there a way to verify under which account initdb was running? Jochem
>> A new beta-release of the win32 gui installer has been uploaded to
>> pgfoundry.
>>
>> Postgresql is the snapshot from 20040731, with the win32
>versioning/icon
>> patch added, as well as the initdb auth patch (in the patch queue).
<snip>
> The files belonging to this database system will be owned by
>user "postgres".
^^^^^^^^
<snip>
>
>I am running this while logged in on a domain account that has
>both local and domain admin priviledges. I have created the user
>"postgres" and granted it "Log in as a service" priviledges.
>Permissions on the C:/Program Files/PostgreSQL/7.5/data/ dir are
>set by the installer in such a way that the postgres user has
>Change, and the rest has nothing.
>
> From the error it appears that initdb was running as 'me'
>instead of 'postgres'. Is there a way to verify under which
>account initdb was running?
The line underlined above indicates the account that initdb runs under.
Can you check if you can run initdb manually against that data directory
when logged in as "postgres"?
(It should not work as yourself - initdb will terminate because you are
running with admin privs)
//Magnus
Magnus Hagander wrote: > > Can you check if you can run initdb manually against that data directory > when logged in as "postgres"? How do I get it installed without a rollback then? If I choose to install without initializing a cluster the installation tries to start the service which obviously fails. I then have the option to retry or to cance, but not to proceed and fix later. One other observations: if the installer creates a user account that account is not removed upon rollback. Jochem PS On WinXP Pro SP1 it works flawlessly.
Getting the follow error on install. Note also that I tried running initdb manually with -d I used the postgres account that was created by the install to run initdb, by first running runas /user:postgres "cmd" then typing the init db call Listman The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale C. fixing permissions on existing directory C:/Program Files/PostgreSQL/7.5/data ... ok creating directory C:/Program Files/PostgreSQL/7.5/data/global ... ok creating directory C:/Program Files/PostgreSQL/7.5/data/pg_xlog ... ok creating directory C:/Program Files/PostgreSQL/7.5/data/pg_xlog/archive_status ... ok creating directory C:/Program Files/PostgreSQL/7.5/data/pg_clog ... ok creating directory C:/Program Files/PostgreSQL/7.5/data/pg_subtrans ... ok creating directory C:/Program Files/PostgreSQL/7.5/data/base ... ok creating directory C:/Program Files/PostgreSQL/7.5/data/base/1 ... ok creating directory C:/Program Files/PostgreSQL/7.5/data/pg_tblspc ... ok selecting default max_connections ... 10 selecting default shared_buffers ... 50 creating configuration files ... ok creating template1 database in C:/Program Files/PostgreSQL/7.5/data/base/1 ... FATAL: could not create shared memory segment: No error DETAIL: Failed system call was shmget(key=1, size=1196032, 03600). Deleted file - C:\Program Files\PostgreSQL\7.5\data\pg_hba.conf Deleted file - C:\Program Files\PostgreSQL\7.5\data\pg_ident.conf Deleted file - C:\Program Files\PostgreSQL\7.5\data\PG_VERSION Deleted file - C:\Program Files\PostgreSQL\7.5\data\postgresql.conf child process was terminated by signal 1 initdb: failed initdb: removing contents of data directory "C:/Program Files/PostgreSQL/7.5/data" C:\PROGRA~1\PostgreSQL\7.5\bin>initdb -d -D ..\data -L ..\share Running in debug mode. VERSION=7.5devel PGDATA=../data share_path=../share PGPATH=C:/PROGRA~1/PostgreSQL/7.5/bin POSTGRES_SUPERUSERNAME=postgres POSTGRES_BKI=../share/postgres.bki POSTGRES_DESCR=../share/postgres.description POSTGRESQL_CONF_SAMPLE=../share/postgresql.conf.sample PG_HBA_SAMPLE=../share/pg_hba.conf.sample PG_IDENT_SAMPLE=../share/pg_ident.conf.sample The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale English_United States.1252. fixing permissions on existing directory ../data ... ok creating directory ../data/global ... ok creating directory ../data/pg_xlog ... ok creating directory ../data/pg_xlog/archive_status ... ok creating directory ../data/pg_clog ... ok creating directory ../data/pg_subtrans ... ok creating directory ../data/base ... ok creating directory ../data/base/1 ... ok creating directory ../data/pg_tblspc ... ok selecting default max_connections ... 10 selecting default shared_buffers ... 50 creating configuration files ... ok creating template1 database in ../data/base/1 ... DEBUG: TZ "US/Mountain" match es Windows timezone "Mountain Daylight Time" DEBUG: invoking IpcMemoryCreate(size=1196032) FATAL: could not create shared memory segment: No error DETAIL: Failed system call was shmget(key=1, size=1196032, 03600). DEBUG: proc_exit(1) DEBUG: shmem_exit(1) DEBUG: exit(1) child process was terminated by signal 1 initdb: failed initdb: removing contents of data directory "../data" Deleted file - C:\PROGRA~1\PostgreSQL\7.5\data\pg_hba.conf Deleted file - C:\PROGRA~1\PostgreSQL\7.5\data\pg_ident.conf Deleted file - C:\PROGRA~1\PostgreSQL\7.5\data\PG_VERSION Deleted file - C:\PROGRA~1\PostgreSQL\7.5\data\postgresql.conf Magnus Hagander wrote: > A new beta-release of the win32 gui installer has been uploaded to >pgfoundry. > >Postgresql is the snapshot from 20040731, with the win32 versioning/icon >patch added, as well as the initdb auth patch (in the patch queue). > >Changes since last beta includes: >* PgAdmin shortcuts are now predictably created. >* Startmenu shortcuts are added to start and stop the database (pg_ctl >or service depending on install method) >* Service is set for automatic start instead of manual >* Default encoding is now UNICODE >* There is a base feature with a base directory so the install root can >be changed at one place >* The Next button is now always activated and a popup is shown if the >specified passwords don't match. Workaround the fact that the activation >required the password field to be de-focused before it happened. >* A warning is shown if a service is installed without running initdb >when there is no database in the directory already. >* The installer now verifies that the user specified has Log on as a >service right, and optionally grants it. >* The installer now verifies that the user specified is not an >administrative user, and refuses to continue if it is. >* The installer now optionally creates a user account (with an optional >random password) for the service. > > >Plus a few other minor things. > >This addresses many of the issues brought up since the last beta, but >not all. Please see the trackers on pgfoundry.org/projects/pginstaller >for status on the other items, or to add new items. > > >If you are upgrading from the previous snapshot, you'll have to >uninstall the old version first. You can do this from Add/Remove >progrmas, or by running "msiexec /x postgresql-7.5-devel.msi" on the >commandline. This will not remove the data directory. >You can run the new version on the same data directory, but we'd >appreciate testing of clean installations anyway. In that case, >pg_dump/reload and manual removal of the data directory is needed. (Full >testing would also require removal/recreation of the service account, of >course). > > >As before, please post your feedback to the mailinglist on >pgfoundry.org, or use the trackers. > >And thanks for all the feedback on the first beta! > >//Magnus & Dave > > >---------------------------(end of broadcast)--------------------------- >TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) > >
Magnus Hagander wrote: > > Can you check if you can run initdb manually against that data directory > when logged in as "postgres"? Since I can not even run notepad or dir when logged in as "postgres", I suspect the installer is not at fault. Sorry for the false alarm. Jochem
I tried three scenarios on XP Professional. 1) Install everything and use all defaults worked perfectly 2) Install everything, use a custom path of 'c:\program files\pgsql', and have an old version (1.0.2) or Pgadmin 3 installed on the machine. This got things confused, not sure if it was due to me leaving off the trailing '\' on the path, or having the old Pgadmin 3 installed. What happened was the "setting permissions" scanned the *entire* c drive, moer than once I think. The installer showed a message saying Pg did not start (but it did). At this point I uninstalled, deleted the Postgres user and proceeded to 3) 3) Install everything, use a custom path of 'c:\program files\pgsql\', and remove pgadmin 3 (1.0.2) *before* installing. worked perfectly. regards Mark Quoting Magnus Hagander <mha@sollentuna.net>: > A new beta-release of the win32 gui installer has been uploaded to > pgfoundry. > > Postgresql is the snapshot from 20040731, with the win32 versioning/icon > patch added, as well as the initdb auth patch (in the patch queue).
> -----Original Message----- > From: pgsql-hackers-win32-owner@postgresql.org > [mailto:pgsql-hackers-win32-owner@postgresql.org] On Behalf > Of markir@coretech.co.nz > Sent: 02 August 2004 23:18 > To: Magnus Hagander > Cc: pginstaller-devel@pgfoundry.org; > pgsql-hackers-win32@postgresql.org > Subject: Re: [pgsql-hackers-win32] New pginstaller beta > > I tried three scenarios on XP Professional. > > 1) Install everything and use all defaults > > worked perfectly > > > 2) Install everything, use a custom path of 'c:\program > files\pgsql', and have an old version (1.0.2) or Pgadmin 3 > installed on the machine. > > This got things confused, not sure if it was due to me > leaving off the trailing '\' on the path, or having the old > Pgadmin 3 installed. > > What happened was the "setting permissions" scanned the > *entire* c drive, moer than once I think. The installer > showed a message saying Pg did not start (but it did). > > At this point I uninstalled, deleted the Postgres user and > proceeded to 3) > > > 3) Install everything, use a custom path of 'c:\program > files\pgsql\', and remove pgadmin 3 (1.0.2) *before* installing. Thanks for the report Mark. I can't reproduce this here - can anyone else confirm this problem? Regards, Dave.