On 12/8/06, Adam Radlowski <adamr@informatyka.gdansk.pl> wrote:
> I had problem such this. I've got 8.1.3 client and 8.0.6 server. But
> psql 8.1.3 warned me, that some \? functions can not work properly. I've
> resolved this problem in very simply way.
thanks.
my problem is resolved as i mantain symbolic links to different pgsql versions
in /opt/usr/local i just gave full path to psql binary of old version instead
of psql.
My concern was that it is quite likely that developers willl
FAIL to see the warning if they are presented with the
psql prompt despite mismatch of major version numbers.
IMHO for major version mismatch psql should not present the
user with a prompt at all as certain commands are most likely
not work.
Regds
Mallah.
I got binary psql from 8.0.x
> and run. Psql program is a client program, that uses libpq library, so
> it is (I think) no difference until the libpq includes correct and
> enough routines to call them from psql. I've tested for example my own
> application compiled with 8.1.3 libpq on 7.4.8 libpq, or compiled with
> 8.0.7 on 8.1.3. But the not use functions, like \?. No problems. But the
> \? functions in psql are implemented (I think) in other way and are
> version specific, becouse the consttruction of information part of
> database is not compatible between versions 8.0.x and 8.1.x and 8.2.x
> (the first two numbers of a version are signifficant in this case).
> Brgds
> Adam
>
> Rajesh Kumar Mallah wrote:
>
> > Hi,
> >
> > We connected psql 8.2.0 accidently to postmaster ver 8.1.5.
> > \d tablename does not work.
> >
> > should psql at least warn like pg_dump does in case
> > of such client server version mismatches ?
> >
> > regds
> > mallah.
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: In versions below 8.0, the planner will ignore your desire to
> > choose an index scan if your joining column's datatypes do not
> > match
> >
> >
>
>