This is a discussion on Re: Mediawiki 1.10 and PG 8.3 upgrade within the Pgsql General forums, part of the PostgreSQL category; --> If upgrading MediaWiki to a version that supports postgres 8.3, another option could be to export from the old ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| If upgrading MediaWiki to a version that supports postgres 8.3, another option could be to export from the old db as XML (using the Special:Export page) then import once the new wiki's installed with a blank database - that's what I'm going to try, I've had problems upgrading MediaWiki databases in the past, possibly due to customised installations. This should hopefully render any database issues irrelevant. You need to know the names of the pages to export, but could get those with a simple query direct to the database like SELECT pagetitlecolumn FROM tablewherepagetitlesarestored; - see http://www.mediawiki.org/wiki/Manual Regards Oliver On 30 May 2008, at 22:10, pgsql-general-owner@postgresql.org wrote: > http://www.postgresql.org/docs/8.3/s...migration.html > http://www.postgresql.org/docs/8.3/static/tsearch2.html > > I haven't personally tried that procedure with MediaWiki, though. |
| |||
| -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > If upgrading MediaWiki to a version that supports postgres 8.3, > another option could be to export from the old db as XML (using the > Special:Export page) You can also use the dumpBackup.php tool in the maintenance directory. The XML this dumped does not include the mwusers table, so it's not entirely helpful. I spoke too soon when I said earlier all one needs is php update.php. There are some serious tsearch2 issues that prevent you from dumping the old database and importing into the new version, even with the tsearch2 compatibility stuff. I'm creating some workarounds, and will report back. Doing a --data-only dump and creating the schema anew from maintenance/postgres/tables.sql should work, although not if you've made any schema changes, obviously. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200805311103 http://biglumber.com/x/web?pk=2529DF...9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkhBaX4ACgkQvJuQZxSWSsg2lgCfWn5bPrgZFf p+Tf/rZFlqSEIm AB8AoKfl/ooepXLbjzh3ql4GGuk86MJT =yQ9w -----END PGP SIGNATURE----- -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general |
| ||||
| -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Rather than try to document my experiences here in an email thread, I created a wiki page to document the database upgrade process in general for MediaWiki. Please look it over and edit it as needed: http://www.mediawiki.org/wiki/Manual:Upgrading_Postgres - -- Greg Sabino Mullane greg@turnstep.com End Point Corporation PGP Key: 0x14964AC8 200806041024 http://biglumber.com/x/web?pk=2529DF...9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkhGpcAACgkQvJuQZxSWSsgcPACgqDlcqt4dxf gwRfyehMuBy0lZ b9sAnjBax4Na+gRxYsdOItGciCKvMjjO =qFJ9 -----END PGP SIGNATURE----- -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general |