| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | "Wade D(dot) Oberpriller" <oberpwd(at)anubis(dot)network(dot)com> |
| Cc: | general-help postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: initdb on build machine and moving to production machine |
| Date: | 2001-01-11 23:09:04 |
| Message-ID: | Pine.LNX.4.30.0101120007310.1080-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Wade D. Oberpriller writes:
> I want to be able to do an initdb on a build machine and then copy this new
> database to a production machine and run with it. One thing I have noticed is
> that initdb needs an absolute path, so if I copy the database it needs to
> reside in an identical location as where it was initialized.
No. The path is only used within initdb to find the directory. It's not
saved anywhere.
> Is there anyway to overcome this, that is can a database be initialized and
> copied to another locationa and still work?
This should work painlessly if both machines are the same platform.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2001-01-11 23:23:25 | Re: PostgreSQL v7.1BETA3 Bundled and Available ... |
| Previous Message | Peter Eisentraut | 2001-01-11 22:55:18 | Re: PostgreSQL v7.1BETA3 Bundled and Available ... |