Re: [Bacula-users] Migrating form mysql to postgresql: Loading the database takes very long
2011-06-27 07:41:25
Am 26.06.2011 00:18, schrieb Gavin McCullagh:
> It seems you need to drop --quick which is implied in --skip-opt. The
> resulting command that I'm working with at the moment is:
>
> mysqldump -t -n -c --compatible=postgresql --skip-quote-names --quick \
> --lock-tables --add-drop-table --add-locks --create-options
> --disable-keys \
> --extended-insert --set-charset -u bacula -ppassword bacula \
> | grep -v "INSERT INTO Status" \
> | sed -e 's/0000-00-00 00:00:00/1970-01-01 00:00:00/g' \
> | sed -e 's/\\0//'> bacula-backup.sql`
>
> That being said, this is untested so far -- I haven't actually done the
> migration -- but this is the plan thus far :-)
>
> Feedback/corrections welcome...
Thanks for this nice line :)
The whole process now took less than three hours, whereas before I
had to quit it after three days.
Not being an SQL expert that saved me a lot of man-reading.
Thanks again!
Marcus
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
|
|