Re: FWD: Re: Updated backslash consistency patch - Mailing list pgsql-hackers

From Tom Lane
Subject Re: FWD: Re: Updated backslash consistency patch
Date
Msg-id 9361.1232044520@sss.pgh.pa.us
Whole thread Raw
In response to Re: FWD: Re: Updated backslash consistency patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: FWD: Re: Updated backslash consistency patch  ("Robert Haas" <robertmhaas@gmail.com>)
List pgsql-hackers
I wrote:
> "Robert Haas" <robertmhaas@gmail.com> writes:
>> I'm not sure whether you're endorsing that approach or panning it, but
>> -1 from me.  We have always had \d or \dt for user tables and \dS or
>> \dtS for system tables.  No one is complaining about this AFAICS, so
>> we should \df be any different?

> You're ignoring the fact that tables and functions are different and
> are used differently.

BTW, it might be worth pointing out that \d has never worked like that;
for instance "\d pg_class" gives me an answer anyway.  So holding up the
table behavior as a model of consistency that other \d commands should
emulate is a pretty weak argument to begin with.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Updated backslash consistency patch
Next
From: "Robert Haas"
Date:
Subject: Re: FWD: Re: Updated backslash consistency patch