Re: proposal: more practical view on function's source code - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: proposal: more practical view on function's source code
Date
Msg-id 4BA65EBF.3020808@dunslane.net
Whole thread Raw
In response to Re: proposal: more practical view on function's source code  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-hackers

Craig Ringer wrote:
> On 21/03/2010 8:03 PM, Pavel Stehule wrote:
>> Hello
>>
>> Current form of function detail isn't too practical (see screenshot 1)
>>
>> we can move source code to separate area (maybe we can add rownumbers)
>>
>> see screenshot 2 (it is only mockup, real implementation can be more
>> inteligent in rows numbering)
>
> Ideally, the output of the source listing could be used as input to 
> CREATE OR REPLACE FUNCTION without excessive massaging. Those line 
> number prefixes make it hard to grab the output of \df+ and do 
> something useful with it. Sure, vim's column-edit takes care of them 
> quickly enough, but it's still a pain, and if the output format is to 
> be changed it might be nice to see it change in a way that makes it 
> easier to re-use that source listing.
You can get there sorta by doing "\pset format unaligned" followed by 
"\df+ funcname"

But I agree it's annoying to have to do two commands.

cheers

andrew


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: proposal: more practical view on function's source code
Next
From: Tom Lane
Date:
Subject: Re: proposal: more practical view on function's source code