From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
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>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: initdb failure with Postgres 8.4.4 |
Date: | 2010-12-13 15:58:52 |
Message-ID: | 8338.1292255932@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"BRUSSER Michael" <Michael(dot)BRUSSER(at)3ds(dot)com> writes:
> 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.
If that ever worked, with any version of Postgres, I'd be astonished.
Here is what you should do:
1. Build Postgres with --prefix set to some empty directory.
2. Run install.
3. Bundle up the resulting install tree as part of your tarball. Do not
editorialize upon the relative locations of its contents.
4. Drop the install tree wherever you want on the target machine.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-12-13 15:59:27 | Re: SQL/MED - file_fdw |
Previous Message | Tom Lane | 2010-12-13 15:55:22 | Re: hstores in pl/python |