Re: Remove "Source Code" column from \df+ ? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Remove "Source Code" column from \df+ ?
Date
Msg-id 15028.1476285415@sss.pgh.pa.us
Whole thread Raw
In response to Re: Remove "Source Code" column from \df+ ?  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Remove "Source Code" column from \df+ ?
Re: Remove "Source Code" column from \df+ ?
Re: Remove "Source Code" column from \df+ ?
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> * Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote:
>> I'm OK with just removing all the source codes from the \d family and
>> using the \s family instead.

> Ok, great, thanks for clarifying that.  Since we only have '\sf' today,
> I think the prevailing option here is then to make the change to
> removing 'prosrc' from \df+, have an 'internal name' column, and have
> users use \sf for functions.

I'm not sure that Peter was voting for retaining "internal name", but
personally I prefer that to deleting prosrc entirely, so +1.

> Personally, I like the idea of a '\sv' for views, though we should
> discuss that on a new thread.

We have \sv already no?

I'm kind of -1 on removing view definitions from \d+.  It's worked like
that for a very long time and Peter's is the first complaint I've heard.
I think changing it is likely to annoy more people than will think it's
an improvement.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Remove "Source Code" column from \df+ ?
Next
From: Peter Eisentraut
Date:
Subject: Re: [COMMITTERS] pgsql: Extend framework from commit 53be0b1ad to report latch waits.