hawk__

I’ve had a quick look into the plugin’s source code, and it uses it’s own tables and SQL code.

I was about to ask you for the logs from pg4wp’s log subdir :

You should have some error logs in pg4wp’s log subdirectory.
These could help me make a fix if you don’t mind sending them to me (you can replace sensitive data if you want).

If you have no file in this subdir, please check that you have this in your ‘db.php’ file :
define( ‘PG4WP_LOG_ERRORS’, true);

You can send the log files as a compressed archive to pg4wp[at]hawkix.net

I’ll send a modded pg4wp for you to test…

This “incompatibility” is effectively due to the fact that the 2 plugins do replace WP’s DB class with a customized one.

I don’t have enough free time for now to dive into this problem, but I think it may be possible to somewhat “chain” pg4wp and W3 Total Cache (by having one load the other).

I’ll try to spend some time on this in the next few weeks

I didn’t notice your question before because you didn’t post it in PG4WP support forum (https://www.ads-software.com/extend/plugins/postgresql-for-wordpress/support/).

The possibility to specify the port on which to connect for the database has been integrated in PG4WP 1.3.0 (released today).

You should upgrade your PG4WP and then you can set the port in the hostname for database connection in WordPress configuration page :
HOSTNAMEorIP:PORT eg localhost:3128

PG4WP officially supports WordPress 3.4 and PostgreSQL 9.1+, don’t hesitate to report any problem.

Hi !

You don’t tell which version of PG4WP you were using, so I assume 1.2.2 (which was the latest stable version when you posted)…

I’ve integrated a similar patch in PG4WP 1.3.0b1 and so the new stable version (released earlier today) has it included ??

Anyway, thank you for your effort, please keep me informed if you have any issue using PG4WP.

PG4WP 1.3.0b1 was published and has support for PostgreSQL 9.1+.

You should test it if you still want to install WordPress with PostgreSQL 9.1+.

I also changed my contact form to have a better history of contacts.

I published a beta for the upcoming release of PG4WP which is mainly aimed at PostgreSQL 9.1+ support.

You can download this version from the developers page in the plugin directory.

Hi all

mxa5942’s workaround will resolve the installation problem itself, but you’ll encouter problems using WordPress as MySQL quoting is not accepted by PostgreSQL 9.1+ without setting standard_conforming_strings = off in your postgresql.conf file.

I’m going to work on a fix for this problem in the coming weeks, watch out for the next release ??

Hi !

Sorry for not answering before, I’ve had quite much work for the last months and I had to suspend PG4WP work.

Chances are that your Worpdress setup can’t complete because PostgreSQL 9.1+ has standard_conforming_strings set to ‘on’ by default in postgresql.conf

For now PG4WP doesn’t officially work with PostgreSQL 9.1+ without setting standard_conforming_strings to ‘off’ (I’m going to work on a workaround in the next weeks).

Hi

PG4WP 1.2.2 was not tested yet with WordPress 3.3.x

However, I had reports saying PG4WP 1.2.2 works ok with WP 3.3 but I don’t know if these concern fresh installs or upgrading from a previously working installation.

I think your problem comes from the errors you got when installing.
If using PostgreSQL 9.x, this problem may be solved by setting standard_conforming_strings = off in your postgresql.conf file.

See this article for details.

Hope this will help you.

PG4WP is intended to handle database upgrades correctly.

Although you should do a backup before you run the upgrade (we never know what could go bad), you can run the upgrade.

You’ll get some error messages in your postgresql logs, due to WordPress trying to recreate already existing indexes (WordPress thinks they don’t exist yet), they can be safely ignored.

The Hawkix Blog (https://www.hawkix.net home of PG4WP) is running the latest release of PG4WP and was upgraded smoothly from WordPress 2.9 to WordPress 3.2.1

Hello

I’m currently updating PG4WP make it fully compatible with WordPress up to version 3.2.1

I’ve released a beta that works ok on my setup, if you want to give it a try you’ll find a direct link on https://www.hawkix.net.

If upgrading PG4WP from any earlier version, don’t forget to replace the db.php file with the one from the pg4wp/ directory.

Beta 1.2.0b1 should at least have all the issues found in this topic resolved.

PG4WP was recently released in version 1.1.0 and it has full support for WordPress 2.9.2

Now I’ll be working on improving the code to remove some annoying problems that are due to the current implementation.

My plugin is almost stable by now, and I use it on my blog every day.

Version 1.0.0 is almost ready and will be released soon, including a bunch of code reorganisation.

Just a post to inform readers that my plugin is now almost stable and works with WP versions 2.5.1 up to WP 2.8

Hello

I made a hack a year ago that I burried out some days ago.

If you wish to try it, I’d love to get feedback about it.
You can download it from https://www.hawkix.net.

It works out of the box to install a basic WordPress Blog on a PostgreSQL database, my blog works with it.

My blog is written in French only for now, I’ll set up an multi-lingual version soon.

If you try it, just be warned that :
– when I made it, the plugin was a quick and dirty hack intended just to be able to install WordPress on a PostgreSQL-only development computer
– I don’t think it is “production-quality” yet, but I hope to make it so
– it works with a basic WordPress install, I don’t know if any plugin would work OK with it

My idea is to make it possible to have a maintainable alternative to MySQL for WordPress, and PostgreSQL is just the first one.