Tino Wildenhain wrote:
>>> well, i agree with you that postgresql is stable and solid. one of my
>>> biggest gripes with postgresql is that it's not "lightweight" or
>>> "simple" enough. some things are awkward/a chore to do in postgresql,
>>> while simple in other dbms's. in mysql, i can shut down mysqld, copy the
>>> database directory to another installation, and be done with it. ms
>>
>> And why it will not work with postgresql? Shutdown the database, backup
>> the data directory and restart with another option.
>>
>> Just because you can backup database online does not mean you can not do
>> a off- line backup.
sorry, i was actually talking about moving one database from one
installation to another, not about offline backup. or can i do it with
postgresql too? afaik, each database has a unique id (unique to the
local installation/the 'template1' database). what if this id collides
with the target installation?
--
dave
