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

From Heikki Linnakangas
Subject Re: FWD: Re: Updated backslash consistency patch
Date
Msg-id 496F61CA.60707@enterprisedb.com
Whole thread Raw
In response to Re: FWD: Re: Updated backslash consistency patch  (Bruce Momjian <bruce@momjian.us>)
Responses Re: FWD: Re: Updated backslash consistency patch  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian wrote:
> Peter Eisentraut wrote:
>> Bruce Momjian wrote:
>>>> Here's an updated version of the psql backslash patch that should
>>>> apply cleanly to the current HEAD. To recap, this makes all the \dX
>>>> commands (most importantly to most: \df) work like \dt does, in that it
>>>> requires a \dXS to see system items. See the archives for much more
>>>> discussion on the issue.
>>> Patch applied, thanks.
>> This patch has annoyed me twice in two days now, and similarly with 
>> other people I know.  Having to type \dfS now is about the worst loss of 
>> usability in psql that I can recall.  Can we reconsider or revert this?
> 
> Well, \dT is even worse.  ;-)  (How many users have user-defined types?)
> 
> The basic goal of the patch was to make 'S' consistent for all \d
> backslash commands, and we had a lot of discussion about it, and many
> people asked for it (I can't find my user functions).  It is hard to
> argue that our previous behavior was logical (though perhaps useful).

Consistency is nice, but I'm used to typing \df pg_foobar() as well. 
Could we make plain "\df" list only user functions, but "\df XXX" search 
for system functions as well? And the same for all \d* commands, for the 
consistency.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: FWD: Re: Updated backslash consistency patch
Next
From: Stephen Frost
Date:
Subject: Re: New patch for Column-level privileges