Re: review: psql: edit function, show function commands patch - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: review: psql: edit function, show function commands patch
Date
Msg-id AANLkTik488Ow2QOqJ41QJR=-f68yAYJOrxxTPveKebZY@mail.gmail.com
Whole thread Raw
In response to Re: review: psql: edit function, show function commands patch  ("David E. Wheeler" <david@kineticode.com>)
List pgsql-hackers
2010/8/9 David E. Wheeler <david@kineticode.com>:
> On Aug 8, 2010, at 8:38 PM, Tom Lane wrote:
>
>> Um, but \sf *doesn't* give you anything that's usefully copy and
>> pasteable.  And if that were the goal, why doesn't it have an option to
>> write to a file?
>>
>> But it's really the line numbers shoved in front that I'm on about here.
>> I can't see *any* use for that behavior except to figure out what part of
>> your function an error message with line number is referring to; and as
>> I said upthread, there are better ways to be attacking that problem.
>> If you've got a thousand-line function (yes, they're out there) do you
>> really want to be scrolling through \sf output to find out what line 714
>> is?
>
> Suggestion:
>
> \sf without line numbers
> \sf+ with line numbers

it did it :)

Pavel

>
> Best,
>
> David
>


pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: review: psql: edit function, show function commands patch
Next
From: Markus Wanner
Date:
Subject: Re: dynamically allocating chunks from shared memory