From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | BRUSSER Michael <michael(dot)brusser(at)3ds(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: initdb failure with Postgres 8.4.4 |
Date: | 2010-12-13 15:53:54 |
Message-ID: | 1292255503-sup-8485@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from BRUSSER Michael's message of lun dic 13 12:34:49 -0300 2010:
> I'm not sure if our current approach would work with v8.4. This is what we do in the nutshell:
> - build Postgres
> - do not run install
> - collect all generated libraries, executables and input files and pack them along with other app
> - distribute the tar-ball to the customer
> - untar and install the app
> the installation script at some point calls initdb, create database, createlang, create user,
> it creates config files... done.
I think this procedure needs to be fixed. It should be:
- build Postgres
- install
- collect the files, pack
- distribute
- unpack to the destination directory
Since our packaging is (supposed to be) relocatable, you can install in
the customer's machine at a different destination directory, and it
should work. If it doesn't, report it as a bug.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-12-13 15:55:22 | Re: hstores in pl/python |
Previous Message | Tom Lane | 2010-12-13 15:50:43 | Re: ALTER EXTENSION ... UPGRADE; |