@tony at marston-home dot demon dot co dot uk, it doesn't really help to open a new ticket if you gave no feedback in the previous one. Please check what requinix was asking you there, then lets see further.

Thanks.

No, I did not edit the wrong php.ini file. I did not edit any file at all as I already had a working PHP installation. All I did was overwrite my 5.5.18 installation with the files for 5.6.4, and the pgsql extension simply stopped working.

Ok, so this is checked. Please do the following


cd <5.6 folder path>
php -n -d extension_dir=ext -d extension=php_pgsql.dll -m

do you see the pgsql ext loading?

Thanks.

This is the output I get from that command:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

F:\PHP5>php -n -d extension_dir=ext -d extension=php_pgsql.dll -m
[PHP Modules]
bcmath
calendar
Core
ctype
date
dom
ereg
filter
ftp
hash
iconv
json
libxml
mcrypt
mhash
mysqlnd
odbc
pcre
PDO
pgsql
Phar
Reflection
session
SimpleXML
SPL
standard
tokenizer
wddx
xml
xmlreader
xmlwriter
zip
zlib

[Zend Modules]


F:\PHP5>

The pgsql extension is still not showing in phpinfo().

With this you see that the pgsql ext itself isn't broken. You need to revisit your configuration under Apache. Please note, that Apache does chroot away from the php dir. So check what you have on the %path% when Apache starts. Also ensure that php.ini has correct path to the extension_dir. 

Thanks

Also, from what i see in the bug #68645 - ext with different SAPI, and - as you told you was doing an overwrite. That probably something on shouldn't do. Yes, you might be able reuse the php.ini (but check also), but don't do overwrite - replace the dir. I'd advise you to start from backing up your old f:\php5 and extracting new fresh zipball, then putting the old/revisited php.ini in there.

Thanks.

I did not change my Apache configuration, nor did I change my postgresql installation. My httpd.conf file contains the same LoadFile "E:\Program Files (x86)\PostgreSQL\9.2\bin\libpq.dll" directive that it did with the previous PHP installation. I did not overwrite the php.ini file as that exists in the C:/windows directory and not the F:/PHP5 directory.

Your reference to me using a different SAPI is incorrect.

My extension_dir setting remains unchanged at F:/php5/ext

I repeat, all I have done is upgrade the files in my F:/PHP5 directory. The pgsql extension no longer shows up in phpinfo() and is therefore not usable.

Ok, now as you've mentioned libpq.dll, i probably see what is wrong. It is so, that the libpq.dll is supplied with PHP. Please use it. 

From what i can see, the libpq.dll from the postges distribution is compiled with VC10 while we use VC11 for PHP 5.5+. It colud be a luck that the method you've described was working at all, but it's definitely not the right way.

Ah, and seems you was pulling a 32 bit libpq.dll, does that match your php bitness?

Thanks.

Ah, my typing error. Not SAPI, but API. As it was showing "different module API" error, so i suppose something went wrong with your overwriting. Also - even within the same minor version some files could have gone or changed. So it's always better not to overwrite, but to replace the whole dir.

Yes, I am using 32bit PHP although Windows 7 is 64 bit.

I have replaced file "E:\Program Files (x86)\PostgreSQL\9.2\bin\libpq.dll" with the latest one from the PHP installation, and the extension is working now.

Many thanks.

Great! Most of the dependency DLL are delivered in the PHP zipball. They're strongly recommended to use. Though there are some not delivered for various reasons (like the oci one).

Thanks.