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

Re: BUG #2701: PQserverVersion function missing

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Seth Gordon <sethg+pg(at)ropine(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2701: PQserverVersion function missing
Date: 2006-10-24 21:11:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> >>> Actually, the 8.0.X libpq function would still report 70401 if connected
> >>> to a 7.4.1 database,
> >> 
> >> That was exactly the reason why the docs were written like that.  Using
> >> two examples that are both from the same major release doesn't seem to
> >> me to be an improvement.
> > Actually, the problem with 8.0.X is that the major version number had a
> > zero in it.  8.1 does not, so I think it is actually better to use the
> > same major version number in both examples.
> You're ignoring the point at hand, which is exactly that the libpq
> function will work when connected to servers older (in fact much older)
> than it is.

Fine, but the examples are not trying to show that.  The example is to
show the trailing zero added for 8.1.

  Bruce Momjian   bruce(at)momjian(dot)us

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-bugs by date

Next:From: Jeff DavisDate: 2006-10-24 22:32:05
Subject: Re: Bug related to out of memory condition (more information)
Previous:From: Mareks MalnacsDate: 2006-10-24 20:53:07
Subject: BUG #2719: configure script does not accept --enable-locale --enable-multibyte=UNICODE options

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