From: | Alvaro Herrera <alvherre(at)surnet(dot)cl> |
---|---|
To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: psql backslash consistency |
Date: | 2005-05-27 18:09:16 |
Message-ID: | 20050527180916.GC10164@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Fri, May 27, 2005 at 01:58:05PM -0400, Robert Treat wrote:
> On Fri, 2005-05-27 at 03:45, Peter Eisentraut wrote:
> > Tom Lane wrote:
> > > Greg Sabino Mullane <greg(at)turnstep(dot)com> writes:
> > > > Attached is my "backslash consistency" patch which basically makes
> > > > all the backslash commands behave as \dt does: \d* shows non-system
> > > > objects, and \d*S shows system objects.
> > >
> > > Could we have a way to turn this off? At least for functions and
> > > operators? For my usage, at least, this will be a serious step
> > > backwards in usefulness.
>
> Do you have an implementation in mind? I'm having trouble coming up with
> a way to do it cleanly.
How about a psql config option? It should default to show only
non-system objects, as that is the most generally useful behavior.
--
Alvaro Herrera (<alvherre[a]surnet.cl>)
A male gynecologist is like an auto mechanic who never owned a car.
(Carrie Snow)
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2005-05-27 19:09:35 | Re: psql backslash consistency |
Previous Message | Tom Lane | 2005-05-27 18:02:33 | Re: psql backslash consistency |