Idea - fallback mode for psql backslash commands using information_schema

From: "Dawid Kuroczko" <qnex42(at)gmail(dot)com>
To: "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Idea - fallback mode for psql backslash commands using information_schema
Date: 2008-12-29 14:19:50
Message-ID: 758d5e7f0812290619r1f993b8bhf76db277472e66b3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

I think I've got a nice TODO item for psql client:

When a client connects to a database which has unknown (newer)
version it might be advisable to 'fallback' some commands to use
INFORMATION_SCHEMA instead of system catalogs.

For instance when connected to 8.4dev server using 8.3 client,
after issuing \d foo_table you get:
ERROR: column "reltriggers" does not exist
LINE1: SELECT relhasindex, relkind, relchecks, reltriggers, relhasr....

Of course the information_schema will probably be less efficient
and won't have PostgreSQL-specific items like 'Has OIDs', but
the user experience should be better.

My question is: does it look like a good TODO item? :)

Best regards,
Dawid
--
.................. ``The essence of real creativity is a certain
: *Dawid Kuroczko* : playfulness, a flitting from idea to idea
: qnex42(at)gmail(dot)com : without getting bogged down by fixated demands.''
`..................' Sherkaner Underhill, A Deepness in the Sky, V. Vinge

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kurt Roeckx 2008-12-29 14:24:16 Re: Gcc 4.4 causes abort in plpython.
Previous Message Peter Eisentraut 2008-12-29 13:19:58 Re: SQL/MED compatible connection manager