Re: FWD: Re: Updated backslash consistency patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "Brendan Jurd" <direvus(at)gmail(dot)com>, "Greg Sabino Mullane" <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: FWD: Re: Updated backslash consistency patch
Date: 2009-01-15 18:23:19
Message-ID: 9117.1232043799@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Robert Haas" <robertmhaas(at)gmail(dot)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? The only argument I can see is that
> "it's always been different", but IMHO, making it still be
> inconsistent yet in a sneakier and less intuitive way doesn't seem
> like a step forward.

You're ignoring the fact that tables and functions are different and
are used differently. In particular, most of the system catalogs are
not really meant to be used directly by users, which is surely not
true for functions and operators.

However, having said that, I'm not averse to unifying the behavior
as long as it's done in a sensible fashion. Imposing the old behavior
of \dt on everything else is simply not that sensible fashion.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-01-15 18:25:42 Re: Updated backslash consistency patch
Previous Message Robert Haas 2009-01-15 18:08:51 Re: FWD: Re: Updated backslash consistency patch