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

Re: BUG #6694: 9.2 beta 2 : psql commands \db and \db+ fail

From: Philippe BEAUDOIN <phb(dot)emaj(at)free(dot)fr>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: Ryan Kelly <rpkelly22(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6694: 9.2 beta 2 : psql commands \db and \db+ fail
Date: 2012-06-15 12:50:29
Message-ID: 4FDB2F95.9060800@free.fr (view raw or flat)
Thread:
Lists: pgsql-bugs
Hello,
>>> paf=# \db
>>>
>>> ERROR:  column "spclocation" does not exist
>>>
>>> LINE 3:   spclocation AS "Location"
>>>
>>>           ^
>>>
>>>       
>
>   
>> Are you using the psql provided by 9.2 beta 2? Or an older version? It
>> appears that the version of psql in 9.2 beta 2 does the correct thing,
>> look at src/bin/psql/describe.c line 142 or so.
>>     
>
> Yeah, the OP must be using a 9.1 or earlier psql to connect to the
> 9.2beta2 server showed in his version() output. There's a reason we
> print out a warning like this:
>
>   WARNING: psql version X.a, server version Y.b
>            Some psql features might not work.
>
> when the major version of psql and the server it is connecting to don't match.
>
> Josh
>
>   

Oups ! You are right, I was not using the right psql client version!!!

I am using different pg version for various tests. And I failed here to 
use the right PATH.

Please accept my apologies for the noise.
I will be more careful before reporting the next bug ;-)

Best regards.
Philippe.

In response to

pgsql-bugs by date

Next:From: Magnus HaganderDate: 2012-06-15 14:42:05
Subject: Re: BUG #6689: socket file name convention doesn't allow different IPs and the same port for different pgclusters
Previous:From: Mark SchneiderDate: 2012-06-15 11:33:07
Subject: Re: BUG #6689: socket file name convention doesn't allow different IPs and the same port for different pgclusters

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