Skip to content

Limitations

PG4WP is intended to allow using PostgreSQL as a backend database for WordPress, and all my tests are done against basic WordPress (that is to say, no plugin loaded).

Since version 1.2.0, you shouldn’t notice any rewriting of the data you put on your blog.
Examples : earlier versions removed backticks from your posts and added double quotes around any word containing the text « ID » in capitals.

Many plugins will work without any problem, as long as they don’t use any database code.

You may have problems running WordPress with PG4WP when using other plugins that use the database :

  • Plugins that use direct calls to mysql_*() php functions can’t be handled by PG4WP at all without reworking them to use WordPress’ database functions.
    If you have MySQL support disabled in your PHP setup, such plugins will raise a fatal error as soon as you enable them in WordPress, and you’ll have to manually disable them for your Worpdress to start again (try renaming the plugin file or directory).
    With MySQL support enabled in your PHP setup, you should get a non-blocking error about mysql_connect().
  • Plugins using the WordPress database functions to run their queries may work ‘out of the box’, provided that their SQL queries are standard enough to run directly in PostgreSQL or similar enough to WordPress’ own queries to be already rewritten by PG4WP.
    PG4WP may help you make these plugins to work by logging queries that generate errors (look for `PG4WP_LOG_ERRORS` in the `db.php` file). You may then try to hack PG4WP to add some « translation code » to correct the errors, or post on WordPress.org plugin directory forum to ask for help.

If you happen to try using PG4WP along with another plugin, please keep me informed about your results.