| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jan Urbański <wulczer(at)wulczer(dot)org>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: review: psql: edit function, show function commands patch |
| Date: | 2010-08-09 15:30:24 |
| Message-ID: | AANLkTik488Ow2QOqJ41QJR=-f68yAYJOrxxTPveKebZY@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2010/8/9 David E. Wheeler <david(at)kineticode(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2010-08-09 15:35:41 | Re: dynamically allocating chunks from shared memory |
| Previous Message | David E. Wheeler | 2010-08-09 15:28:57 | Re: review: psql: edit function, show function commands patch |