Skip site navigation (1) Skip section navigation (2)

Re: Finding the pqlib version

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Christoph Zwerschke <cito(at)online(dot)de>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Finding the pqlib version
Date: 2006-02-12 01:58:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Christoph Zwerschke wrote:
> Bruce Momjian wrote:
>  > I was wondering that myself.  I am thinking you would need to use
>  > dlopen() to check for the symbol.  Because the libpq version could
>  > change after you compile, I can't see how you could make it a
>  > configure check unless you said you don't allow changes to libpq
>  > after the build.
> The situation I was talking about is that you have a pre-compiled Python 
> and PostgreSQL installed on your system, together with their header 
> files, but you do not have the full source of Python and PostgreSQL 
> available. I want to be able to compile PyGreSQL as a Python extension 
> which is using functions from the python.dll and the libpq.dll, assuming 
> that the installed header files match the installed dlls.

Right, but assume you want to distribute that binary to others who might
have a different version of libpq.  This is required by packagers and a
run-time test is best in those cases.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to


pgsql-interfaces by date

Next:From: Christoph ZwerschkeDate: 2006-02-12 09:19:42
Subject: Re: Finding the pqlib version
Previous:From: Bruce MomjianDate: 2006-02-12 01:01:52
Subject: Re: Finding the pqlib version

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group