| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
| Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: querying the version of libpq |
| Date: | 2010-10-05 16:41:23 |
| Message-ID: | 26161.1286296883@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> writes:
> On 5 October 2010 16:33, Greg Sabino Mullane <greg(at)turnstep(dot)com> wrote:
>>> How does the driver figure it out?
>>
>> DBD::Pg parses pg_config --version, then passes the information
>> to the C programs for directive fiddling. I certainly hope
>> other drivers are doing the same, as libpq varies across
>> major versions a good deal.
> I would imagine that most libpq wrapping drivers use libpq's
> PQserverVersion(), which returns an integer that looks like 90000.
The real problem is that neither of these can be trusted to tell you the
*library* version. PQserverVersion() is something else altogether,
and I wouldn't want to assume that pg_config exactly matches the library
you're linked to --- if it's even present at all.
We could add a PQlibpqVersion(), maybe, but it would be many years
before client code could rely on that being present.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2010-10-05 16:42:20 | Re: Trying to figure out why these queries are so slow |
| Previous Message | Tom Lane | 2010-10-05 16:35:50 | Re: psql \q hang |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-10-05 16:47:35 | Re: querying the version of libpq |
| Previous Message | Simon Riggs | 2010-10-05 16:40:55 | Re: standby registration (was: is sync rep stalled?) |