Re: initdb on build machine and moving to production machine - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: initdb on build machine and moving to production machine
Date
Msg-id Pine.LNX.4.30.0101120007310.1080-100000@peter.localdomain
Whole thread Raw
In response to initdb on build machine and moving to production machine  (oberpwd@anubis.network.com (Wade D. Oberpriller))
List 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@gmx.net       http://yi.org/peter-e/


pgsql-general by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: RE: Re: Loading optimization
Next
From: Tom Lane
Date:
Subject: Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly