Thread: Bug #828: psql in 7.3 can't talk to 7.1 backends
Philip Warner (pjw@rhyme.com.au) reports a bug with a severity of 4 The lower the number the more severe it is. Short Description psql in 7.3 can't talk to 7.1 backends Long Description acheron:/home/pjw/work/postgresql-7.3/src/bin/pg_dump # /var/lib/pgsql-7.3/bin/psql -p 5432 pjw ERROR: parser: parse error at or near "." Welcome to psql 7.3, 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 pjw=> \d ERROR: parser: parse error at or near "." pjw=>\l ERROR: parser: parse error at or near "(" pjw=> Maybe this is a locale thing; but ISTM it should issue a more meaningful message or refuse to connect. Sample Code No file was uploaded with this report
At 08:23 AM 1/12/2002 -0500, pgsql-bugs@postgresql.org wrote: >Maybe this is a locale thing; but ISTM it should issue a more meaningful >message or refuse to connect. It's a schema thing; can't talk to 7.2 either. Queries sent to backend at startup include: BEGIN; SELECT usesuper FROM pg_catalog.pg_user WHERE usename = 'geochem'; COMMIT I guess we should get the version & refuse to connect... ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 03 5330 3172 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/
Philip Warner <pjw@rhyme.com.au> writes: > I guess we should get the version & refuse to connect... We deliberately don't do that in psql. Not having working backslash commands is not necessarily a fatal lack of functionality --- if you're just going to issue regular SQL commands then psql will work fine with backends of quite different versions. It doesn't seem like a good idea to shut off access to that functionality. A warning at startup about differing versions might be appropriate though. regards, tom lane