It is due to a little change in the client lib and we did not notice that the extension got linked dynamically. You will be able to use the version from the snaps soon (and profit from the client library version 8.3.1).

I've the same problem with Windows XP Professional 32bit SP2, downgrade to 5.2.5 could work too.

Little update:

Libpq and more generally postgresql 8.3.1 do not support VC6 anymore. As we use it for PHP binaries, we will have to go back to 7.x for 5.2.x.

8.3.1 do not support VC6 anymore, while 8.2.7 does support it fine.

"8.3.1 do not support VC6 anymore, while 8.2.7 does support it fine."

I got the same error with vc6 than the ones I got using 8.3.1. Linker error and struct redefinitionfo addrinfo and sockaddr_storage.

If you succeeded to compile it using VC6 (or VC2k5:) please let us know how.

For those looking for a workaround:
1. download libpq.dll from http://support.nusphere.com/viewtopic.php?t=4847 and copy it to your php directory
2. copy libeay32.dll to libeay32-0.9.8e.dll
3. copy ssleay32.dll to ssleay32-0.9.8e.dll

I tested it for a while and seems to work fine.

The safer work around is to use the php 5.2.5 DLL extension.

How difficult can it be to test the most basic things, like starting php, before making a release? Good grief. If you can't do the simple things why do you think people should trust you with the complex things?

"How difficult can it be to test the most basic things, like starting
php, before making a release? Good grief. If you can't do the simple
things why do you think people should trust you with the complex things?"

How difficult it is to test the RC? How difficult it is to report issues before the stable release instead of waiting the final day?

That being said, we do run php and the tests suite before any release. But as some dlls are in the path, I did not detect that the new version (we upgraded libpq in 5.2.6, different version than with 5.2.5) was not static by default. Given the time we had to pack this release, I'm actually very happy that only this error remains (and have an easy work around).

I have tested on 32bit windows that pgsql extension
could loaded but required download some files from pgsql server 8.3.1 binary.

This can be download from offical site or 
I have packed a small archive that could downloaded.

url:
pgserver offical site download
http://wwwmaster.postgresql.org/download/mirrors-ftp?file=%2Fbinary%2Fv8.3.1%2Fwin32%2Fpostgresql-8.3.1-1-binaries-no-installer.zip

small archive.
http://myprojects.srhost.info/download/php_pgsql_files.zip

I have also experienced this problem (Apache 2.2 with PHP 5.2.6 on Windows XP Pro 32-bit). I have found another workaround that may be simpler if your PostgreSQL 8.3 is on the same system as your PHP installation: Simply add your PostgreSQL bin directory ("C:\Program Files\PostgreSQL\8.3\bin" on my system) to your system path. Same effect as copying the necessary libraries to your PHP directory, but perhaps easier to maintain (especially once a fix is found for this problem).

Hi,
After installed WAMP 2.0 on Vista and I have the same problem;(
It will be fixed in next version?

all who want to go back to version 5.2.5, php and using Wamp server, knife download the PHP 5.2.5 addon in www.wampserver.com / en / addons_php.php. Once installed the addon solved this problem with pg_connect

Fixed in 5.3.x snaps. 5.2.7 will have the fix as well.

Or you can use the libs from here:
http://downloads.php.net/pierre/libpq-php-4.4.9-5.2.6.zip