Postgres Pro
Downloads
Home   >   mailing lists

Thread: version mismatch detection doesn't work

version mismatch detection doesn't work

From
Alvaro Herrera
Date:
Hackers,

Seems the functionality to detect old versions of the postmaster with
newer psql doesn't work.  Here, server is 7.2.1:

$ psql alvherre
ERROR:  parser: parse error at or near "."
Welcome to psql 7.3b1, the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms      \h for help with SQL commands      \? for help on internal slash commands
    \g or terminate with semicolon to execute query      \q to quit
 

alvherre=> select version();                          version                           
-------------------------------------------------------------PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC
2.96
(1 row)

alvherre=> 

-- 
Alvaro Herrera (<alvherre[a]atentus.com>)
"Nunca confiaré en un traidor.  Ni siquiera si el traidor lo he creado yo"
(Barón Vladimir Harkonnen)

Re: version mismatch detection doesn't work

From
Bruce Momjian
Date:
I didn't think we were supposed to throw an error on a mismatch, were
we?

---------------------------------------------------------------------------

Alvaro Herrera wrote:
> Hackers,
> 
> Seems the functionality to detect old versions of the postmaster with
> newer psql doesn't work.  Here, server is 7.2.1:
> 
> $ psql alvherre
> ERROR:  parser: parse error at or near "."
> Welcome to psql 7.3b1, the PostgreSQL interactive terminal.
> 
> Type:  \copyright for distribution terms
>        \h for help with SQL commands
>        \? for help on internal slash commands
>        \g or terminate with semicolon to execute query
>        \q to quit
> 
> alvherre=> select version();
>                            version                           
> -------------------------------------------------------------
>  PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96
> (1 row)
> 
> alvherre=> 
> 
> -- 
> Alvaro Herrera (<alvherre[a]atentus.com>)
> "Nunca confiar? en un traidor.  Ni siquiera si el traidor lo he creado yo"
> (Bar?n Vladimir Harkonnen)
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073

Re: version mismatch detection doesn't work

From
Tom Lane
Date:
Alvaro Herrera <alvherre@atentus.com> writes:
> Seems the functionality to detect old versions of the postmaster with
> newer psql doesn't work.

What functionality?  psql has never had such a test.  I think you
are thinking of pg_dump.
        regards, tom lane

Re: version mismatch detection doesn't work

From
Alvaro Herrera
Date:
Tom Lane dijo: 

> Alvaro Herrera <alvherre@atentus.com> writes:
> > Seems the functionality to detect old versions of the postmaster with
> > newer psql doesn't work.
> 
> What functionality?  psql has never had such a test.  I think you
> are thinking of pg_dump.

No, I was thinking of psql.  There was a discussion some time ago about
mismatching versions; I don't know where I got the idea that the
conclusion had been that if versions mismatched, psql would barf.  (The
conclusion was to add the version number to psql.)

-- 
Alvaro Herrera (<alvherre[a]atentus.com>)
"No hay ausente sin culpa ni presente sin disculpa" (Prov. frances)

Re: version mismatch detection doesn't work

From
Greg Copeland
Date:
It was I that originally brought the topic up.  I don't really remember
the exact details but I do seem to recall that the author thought it was
a horrid idea.  Basically and poorly paraphrased the response was that
everyone should use select version() after they connect and if they
don't know to do that or simply forget, that's tough.  I also seem to
recall that even the prospect of having some slash command that showed
psql and back end version was considered a waste and a bad/redundant
idea.  So, as it stands, only the psql version is displayed.

I still think it makes so much more sense to simply state something
like, "Welcome to psql 7.3b1, the PostgreSQL interactive terminal.  You
are currently connected with a 7.1.1 server named 'foobar'".  It's
simple and makes the information very obvious.  It also helps re-enforce
the  name of the server that you've connected with.  I should clarify,
the host name par is not something I originally asked about but does
seem to make sense.  I honestly could care less about the exact text as
making the information obviously available is all that I care really
about.

Personally, I never understood how making even marginally redundant
information readily and obviously available, especially when it can
prevent some potential peril, is a bad idea.  But, for each is own.  ;)

Greg



On Sat, 2002-09-28 at 11:28, Alvaro Herrera wrote:
> Tom Lane dijo:
>
> > Alvaro Herrera <alvherre@atentus.com> writes:
> > > Seems the functionality to detect old versions of the postmaster with
> > > newer psql doesn't work.
> >
> > What functionality?  psql has never had such a test.  I think you
> > are thinking of pg_dump.
>
> No, I was thinking of psql.  There was a discussion some time ago about
> mismatching versions; I don't know where I got the idea that the
> conclusion had been that if versions mismatched, psql would barf.  (The
> conclusion was to add the version number to psql.)
>
> --
> Alvaro Herrera (<alvherre[a]atentus.com>)
> "No hay ausente sin culpa ni presente sin disculpa" (Prov. frances)
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly