If you are transferring your database to the same or newer version of
Postgresql then generally: yes. But take some precautions:
* In the original database: Don't use schema public to store data;
create another schema for that purpose. The reason for this action
is to separate all the postgis functions and view - which resides in
schema "public" - from ordenary data.
* When you make a backup: Only backup your data schema (not public).
This means, that you won't get any version specific, postgis related
stuff into your backup.
* When you restore the backup in another database: First create the
PostGIS extension in this database with the command "Create
extension postgis". This will create the PostGIS extension in the
new database. Secondly: restore your backup. This will restore the
data schema in the database.
If the source and target database system resides on two computers with
the same operating system and same postgres and postgis version, the
above procedure is not needed. Simply make a backup of the source
database and restore it on the target computer.
Regards
Bo Victor Thomsen
AestasGIS
Denmark
Den 05-03-2015 kl. 16:57 skrev Andre Joost:
Am 05.03.2015 um 13:01 schrieb Rémi Cura:
The equivalent way, that is also the simplest, is to dump the tables
(and
related functions/triggers if necessary) into a file, then restore the
table in the target postgis database!
Does this work if the users are on different OS, like
Windows/Linux/Mac OSX, 32bit or 64bit, or maybe different
PostgreSQL/Postgis versions?
greetings,
André Joost
_______________________________________________
Qgis-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-user
