On 06/21/11 22:06, Dan Langille wrote:
> 
> On Jun 21, 2011, at 3:59 AM, Marcus Mülbüsch wrote:
> 
>> I want to migrate my bacula installation from mysql to postgresql, 
>> following the guide in 
>> http://www.bacula.org/5.0.x-manuals/en/main/main/Installing_Configuring_Post.html#SECTION004450000000000000000
>>
>> After dumping and converting the database the sql-file now has 9GiB.
>>
>> I began loading the db into postgres about 18 hours before, but the 
>> process is not yet finished. Is this normal? Or did I miss an important 
>> step?
>>
>> And the command to load the database is indeed:
>>
>> "psql -Ubacula bacula < bacula-backup.sql"
>>
>> and not the mangled version given on the linked page?
> 
> My guess: the output is a series of insert statements, each of which is run 
> in its own transaction.
> Someone else might be able to help more.

It always take longer - usually several times longer - to load any given
SQL symbolic dump back into any SQL DB than it took to dump it in the
first place.  Just for starters, dumping the DB does not alter any
indexes, while when reloading it, all of the indexes need to get
recreated and rebuilt.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
  Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users