Last modified: 2012-08-04 20:48:57 UTC
When I update my MW running on a postgresql database (on Linux, but I guess that does not matter) from 1.11 to 1.13, the update script does not report errors, but any attempt to open a page in MW 1.13 leads to errors because the column revision.rev_parent_id is missing.
Indeed, the scripts for mysql include a statement adding this column but those for postgres don't. I guess the right statement for postgres is
alter table revision add rev_parent_id integer;
but I'm not sure about the exact datatype. And I don't know where to insert this in the update scripts.
I executed this manually, and everything appears to work fine.
I'm wondering whether the update has ever been tested on postgresql, since it seems impossible that this bug is not detected. Is this due to a lack of testers in the postgresql area?
Created attachment 5782 [details]
Patch to updaters.inc
Looks like updaters.inc was only changed to reflect MySQL.
The update for rev_parent_id is right there in the context of your own patch.
I'm releasing 1.14.0rc1 now, I suggest you upgrade directly to that.