Opened 5 years ago
Closed 4 years ago
#4430 closed defect (worksforme)
PostGIS bundle fails in silent install mode for PostgreSQL 11.2
| Reported by: | danielheden | Owned by: | robe |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS Packaging |
| Component: | postgis | Version: | 3.0.x |
| Keywords: | silent install | Cc: |
Description
Trying to install PostGIS using the bundle installer (postgis-bundle-pg11x64-setup-2.5.2-1.exe), the one stackbuilder downloads.
The error message it gives is "PostGIS has to be installed to the PostgreSQL folder."
The problem seems to be that the installer locks for %ProgramFiles%\PostgreSQL\11 instead of %ProgramFiles%\PostgreSQL\11.2
I run with parameters: /S /USERNAME=postgres /PASSWORD=xxxxxx /PORT=5432
And we have been using the same parameter for installing for several year’s without problem before.
The installer works if NOT run in silent mode.
Change History (7)
comment:1 by , 5 years ago
| Milestone: | PostGIS PostgreSQL → PostGIS Packaging |
|---|
comment:2 by , 5 years ago
comment:3 by , 5 years ago
| Owner: | changed from to |
|---|
comment:4 by , 5 years ago
How did you get your thing installed in 11.2? The installation folder is %ProgramFiles?%\PostgreSQL\11
since 11.2 is really a micro release.
comment:5 by , 5 years ago
Forgot to add, that it reads this from the registry so shouldn't matter. That said I haven't had a need for silent installer so haven't tested it recently. Does non-silent install work for you?
comment:6 by , 5 years ago
I saw now that the installer for PostgreSQL is run with this extra argument: —prefix "$PROGRAMFILES64\PostgreSQL\11.2 that explains why it is installed in 11.2. I thought that (11.2) was the default, so that was my mistake.
The installer works if run normally, so there is still a problem but minor one. Since standard pats should work in all install modes.
comment:7 by , 4 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
| Version: | 2.5.x → 3.0.x |
I tested the silent installer with the latest release PostGIS 3.0.2 and seemed to work fine for my PostgreSQL 10, 11, and 12 installs. In theory you shouldn't even need the /USERNAME=postgres /PASSWORD=xxxxxx /PORT=5432 switches as I have the build test database turned off by default. If you were using that as a metric of the installer working, that might be the issue as a database is not created.
It only needs those additional switches for installing the test database. I hadn't tested with those switches.
I'm going to close this out as I can't replicate at least for the latest releases.
System Info: Server 2016 (64-bit) PostgreSQL 11.2 (64-bit) PostGIS 2.5.1 and 2.5.2 (64-bit)