Parson, Damien | 20 May 22:20 2016

Dead openSSL link


On the guide here the openSSL link is no longer valid do you have any other places I can download it from? or any other guides for the windows installer?

Damien Parson 
SDSC IT Systems
(858) 534-9638

Gelenian, Alex | 18 May 16:14 2016

ODBC driver support

I am trying to reuse a local database that I have ported over from an XP machine to Windows 7. We are trying to
recreate the ODBC settings, but the database requires the PostgreSQL ANSI driver.

Is there a way to get the driver on the new computer? It is a critical system for our end users to work.

Alexander Gelenian

Sent from my Verizon Wireless 4G LTE smartphone


Sent via pgsql-odbc mailing list (pgsql-odbc <at>
To make changes to your subscription:
Richard Hetherington | 18 May 14:12 2016

ADO CommandTimeout vs Postgres statement_timeout parameter

Hi, I have been debugging why the ADO CommandTimeout property has no effect on Postgres Queries and I believe that it is being ignored. Is this something that could be modified in a future ODBC Driver release. What I would like to see is an auto prepending of this value to a SQL Query being passed in if set.

I understand that the statement_timeout config parameter in postgres can be configured at the server level, user level and query level. I have tested each and they work as expected. What I wasn't expecting was for my CommandTimeout to be ignored / not passed through.


Set p_objConn = Server.CreateObject("ADODB.Connection")
p_objConn.ConnectionString = "SOME DSN or DSNLess Connection String"
' e.g. DB.ConnectionString = "Driver={PostgreSQL UNICODE};Server=localhost;Port=5432;UID=someuser;PWD=somepassword;Database=somedatabase;"
p_objConn.ConnectionTimeout = 10
p_objConn.CommandTimeout = 30 ' This has no effect on queries run against Postgres !!

If The ADO CommandTimeout value is set, could this be detected, check that the SQL Query hasn't already got a statement_timeout value and if not prepend the SQL Query as follows:

SET statement_timeout = 30000;

SELECT somedata FROM somedatabasetable WHERE somevalue=anothervalue,

Many thanks in advance.

Feel free to contact me if you need any further information.

Kleiber Torrealba | 17 May 17:22 2016


Buenos dias 

quisiera saber donde puedo conseguir o si ustedes me podrian ayudar con unos odbc ya que tengo una base de datos en acces y quiero imigrarla a postgres pero no consigo los controladores adecuados el postgres que estoy utilizando es 9.2

Kleiber Torrealba 
Analista de soporte técnico 
boyan zahariev | 12 May 06:07 2016

ODBC & row level security


I've tried latest ODBC 9.5 32bit driver
and it seems that Row Level Security is not implemented yet.

Is that so, or I'm missing some options to check?

All the Best,
Mateusz Loskot | 10 May 09:56 2016

Case-sensitivity of connection string parameters


I use the psqlODBC 9.2.1 with unixODBC 2.2.14 on Ubuntu 14.04.
Should I expect names of connection string parameters to be case-sensitive?

For instance, if I try DSN-less connection with the following connection
string passed to the ODBC API call SQLDriverConnect:

"Driver={PostgreSQL ANSI};Server=;Database=test;UID=test;PWD=test;"

I get this error:

[unixODBC][Driver Manager]Data source name not found, and no default
driver specified

whereas if I try this one, with the upper-case DRIVER:

"DRIVER={PostgreSQL ANSI};Server=;Database=test;UID=test;PWD=test;"

I get successfully connected.

I've couldn't find any details on the case sensitivity in the FAQ,
release notes or

The only cue might be the connection string in the VB example
at the bottom of this page, where DRIVER is specified in upper-case:

Another cue that suggests case-sensitivity might be important is from
the connection strings database:
and it says:
"Please note that sslmode=require is case sensitive, it should be
written in lower case letters."

But, it is confusing since the
lists this parameter as "SSLmode", but not asd "sslmode".

Finally, I have tried psqlODBC 9.3.4 on Windows and there parameters work
regardless of their case.

Could anyone explain what case of each of the parameters is required useon Unix?

Best regards,
Mateusz Loskot,


Sent via pgsql-odbc mailing list (pgsql-odbc <at>
To make changes to your subscription:

McMillan, Scott A | 2 May 18:45 2016

linux supportability


I'm new to psql-odbc.  

I maintain a Linux tool that uses ODBC (unixODBC) for database access.  I am considering redistributing a
prebuilt psqlODBC driver with my tool to make it as easy as possible for my users to access Postgres
databases.  However, I am wondering if this is wise or not?  (I am not thinking about redistributing
Postgres itself; the user needs to install and setup their database backend.)

How compatible is a binary psqlODBC shared library with different versions or installations of Postgres?

Would it actually be more supportable to have users install the psqlODBC shared library from their Linux
distribution if they don't want to build from source?

What is the recommendation?



Sent via pgsql-odbc mailing list (pgsql-odbc <at>
To make changes to your subscription:
Inoue, Hiroshi | 30 Apr 04:12 2016

Re: ODP: ODP: Problem with the psqlodbc driver

On 2016/04/29 23:20, Adrian Klaver wrote:
On 04/28/2016 10:19 PM, Henryk Dyguś wrote:

Ccing list
Please keep the list in the conversation as that puts more eyes on the problem.

Here's translation.

1st window:

There was a problem with the application odbcad32.exe and needs to close.
Sorry for the inconvenience.
If you are at work, the information you were working on might be lost.
For more information about this error, click here.

2nd window:
Error signature
To view technical information about the error report, click here.

3rd window:
Content error report
The following information about the process will be reported:
The following files will be attached to the bug report:

Thanks for the translation. Unfortunately it seems to be mostly boiler plate wording.

I do not have an answer at this time, though my suspicion is incompatibilities with what ever version of compiler was used and an old version of Windows. Hopefully someone with more knowledge of this can provide more information.

I'm doubtful whether libpq related dlls compiled using vc12 work under Windows XP or not.
Try to replace libpq related dlls (libpq.dll, ssleay32.dll, libeay32.dll and libintl.dll) in C:\Program Files\psqlodbc\0905\bin
with the Binaries from installer version 9.3.12  win32 x86-32

Hiroshi Inoue

Henryk Dyguś | 26 Apr 13:49 2016

Problem with the psqlodbc driver


I have a problem with the new psqlodbc driver (09_05_0210).

After installing the driver and configuring an ODBC source, clicking on the test button,

displays an error message.

This only happens on the hardware platform with an old Athlon XP.

When I install an older version of the driver (09_03_0300), there is no problem.



Henryk Dyguś
Administrator Sieci Komputerowej
Tsubaki-Hoover Polska Sp. z o.o.
23-204 Kraśnik, ul. Fabryczna 6
tel. +48 81 8257407
henryk.dygus <at>




Sent via pgsql-odbc mailing list (pgsql-odbc <at>
To make changes to your subscription:
Alvaro Herrera | 27 Apr 19:27 2016

Re: Fw: new message

rainer.maassen <at> wrote:
> Hello!

Dropped from lists.

Álvaro Herrera      
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


Sent via pgsql-odbc mailing list (pgsql-odbc <at>
To make changes to your subscription:

durga prasad | 26 Apr 01:35 2016

Installing and configuring postgreSQL ODBC on Solaris10


we are seeing the problem, when we run the command "make". please let me know, if you have any idea to solve this issue.

mkdir .libs
rm -fr .libs/ .libs/psqlodbc.* .libs/psqlodbc.*
/usr/ccs/bin/ld -G -z defs -h -o .libs/  info.lo bind.lo columninfo.lo connection.lo convert.lo drvconn.lo environ.lo execute.lo lobj.lo win_md5.lo misc.lo options.lo pgtypes.lo psqlodbc.lo qresult.lo results.lo socket.lo parse.lo statement.lo tuple.lo tuplelist.lo dlg_specific.lo odbcapi.lo multibyte.lo gpps.lo  -lpthread -lnsl -lc
Undefined                       first referenced
 symbol                             in file
recv                                socket.lo
send                                connection.lo
socket                              connection.lo
connect                             connection.lo
ld: fatal: symbol referencing errors. No output written to .libs/
*** Error code 1
make: Fatal error: Command failed for target `'
Current working directory /opt/local/sas/share/PsqlODBC/psqlodbc-7.2.5
*** Error code 1
make: Fatal error: Command failed for target `all'