On Mon, Dec 10, 2007 at 06:16:37PM -0500, Bill Desjardins wrote: > I have a small mogile setup which currently uses mysql and would like > to move it over to postgres but I have a couple questions.. > > - Is the mogilefs code for using postgres stable enough for production usage? I'm using it in production, and I haven't had any long-term problems - it did prod me into getting auto-vacuum properly tuned in my Postgresql (v8.2.4), there was a lot of bloat in the DB from not having it run often enough.
'mogadm stats' doesn't return in a usable time, but that's maybe more of the size of my database. The raw database is 1.8Gb as reported by phpPgAdmin, with 1.9m files (replica count of 4). If you have multiple trackers, the Postgres side could really benefit from moving to Brad's ddlockd instead of using the crappy locking in the database. > - The mogile DB version on my production mysql db is 9 and the new > postgres mogile schema is version 10 (from trunk). Do I need to update > my complete mogilefs installation to match the DB schema version > change? You should be able to load a v9 database into Postgres, and then let mogilefs upgrade it. v9 -> v10 was the replication-policy addition to the replication class. > - what would be the best practice for moving the data over to postgres? > I did some testing for moving the data by using mogdbsetup to create > the DB on postgres and then dumping the data from mysql and importing > it into the new postgres DB. everything went into postgres without > error, but is this a suitable method to recreate the DB on postgres? This should work fine. It's not something I've tested, but I know of no conceptual reason that it should fail. -- Robin Hugh Johnson Gentoo Linux Developer & Infra Guy E-Mail : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
pgpJiv9cElAbG.pgp
Description: PGP signature
