Re: MediaWiki + PostgreSQL is not ready for production?

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: MediaWiki + PostgreSQL is not ready for production?
Date: 2016-07-20 17:33:59
Message-ID: CAOR=d=2riV60-sZYn5-kpM39U7PfikUesMDpmZjqJV_6VSMY9A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jul 18, 2016 at 10:14 PM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
> I found following comment for using PostgreSQL with MediaWiki:
>
> https://www.mediawiki.org/wiki/Compatibility#Database
>
> "Anything other than MySQL or MariaDB is not recommended for
> production use at this point."
>
> This is a sad and disappointed statement for us. Should we help
> MediaWiki community to enhance this?

A few years back I worked at a company that put mediawiki into our
school content management system with postgresql. We had zero issues
with postgresql support, it mostly just worked. Took us about 4 weeks
to get it working and tested and deployed.

The cool bit was that by creating a few triggers and views, we made
mediawiki think it was just sitting on top of the default database
when it fact it was sitting on top of our custom db. Each teacher /
classroom had its own wiki, and we had literally 10s of thousands of
independent wikis running, and they were plenty fast.

--
To understand recursion, one must first understand recursion.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2016-07-20 17:40:01 Re: pg_dump without any SET command in header of output plain text sql file
Previous Message Pavel Suderevsky 2016-07-20 17:30:14 9.5: pg_stat_statement and pgbench execution time discrepancies