Wikimedia Bugzilla is closed!

PostgreSQL support is experimental yet, but is getting better and better :)

Actually PostgreSQL support is getting worse and worse, as it hasn't been 
maintained since major schema changes were made... :)

Is there some place where a "PostgreSQL Bounty" can be made for mediawiki (i.e.
where I can donate 500$ to the person who make this works or somthing like this)
- I think there are a lot of us postgres user out there who are tired of having
to install mysql just to run our wiki. Is there any work on DB abstration in
mediawiki going on ? - I noticed some of the postgres/oracle problems stems from
MySQL's incorrect use of quoting and faulty SQL syntax - these problems could be
overcome by DB abstraction.

For more up-to-date information on the state of PostgreSQL in mediawiki, please
refer to the bugs listed below in the "depends on" section. The quick summary is
that PostgreSQL support is back on track, though we would encourage more
developers to get involved. 

Adding pgsql keyword to summary to help searches.

Created attachment 6105 [details]
requested phpinfo output from comments #c23

Sorry, wrong bug, I tried to attach it to #16937. This attachement can be deleted from here.

Stale

(In reply to comment #8)
> Stale
> 

It's a tracking bug, so it's not supposed to be closed at all, ever.

Adding 'tracking' keyword.

(In reply to comment #9)
> It's a tracking bug, so it's not supposed to be closed at all, ever.

How can we have a tracking bug dupe a keyword? should we?

Is this tracking bug for problems only with Mediawiki, or also extensions?

(In reply to comment #12)
> Is this tracking bug for problems only with Mediawiki, or also extensions?

This is fine to use it for extensions too.