Re: New pginstaller beta

From: markir(at)coretech(dot)co(dot)nz
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: pginstaller-devel(at)pgfoundry(dot)org, pgsql-hackers-win32(at)postgresql(dot)org
Subject: Re: New pginstaller beta
Date: 2004-08-02 22:18:14
Message-ID: 1091485094.1988252b41fbf@mail.coretech.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32

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(at)sollentuna(dot)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).

In response to

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Andreas Pflug 2004-08-03 10:03:56 Re: make fails if path has spaces
Previous Message Marko Zmak 2004-08-02 21:13:15 Re: pg_dumpall on win32