From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Brendan Jurd <direvus(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql wrapped format default for backslash-d commands |
Date: | 2008-05-09 20:50:22 |
Message-ID: | 200805092050.m49KoMM28644@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Brendan Jurd wrote:
> On Sat, May 10, 2008 at 4:37 AM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
> > Brendan Jurd escribi?:
> >> I for one would definitely like backslash commands with very wide
> >> output to be wrapped by default.
> >
> > (At least) one place where I would not like it is in \df+, because
> > wrapped function output would be more difficult to read.
> >
>
> I am a bit conflicted about wrapping on \df. I agree that wrapped
> function code is difficult to read, but what we've got now is
> difficult to read too. Which of the two is more difficult is really a
> matter of personal taste. I guess with \df you have to accept that
> it's always going to be ugly, unless you have a very wide terminal (or
> very short function definitions!).
Oh, good point. I hadn't thought about function bodies being displayed.
Here is an example:
test=> \pset format wrapped
Output format is wrapped.
test=> \pset columns 14
Target width for "wrapped" format is 14.
test=> select prosrc from pg_proc where proname = 'xx';
prosrc
--------------
SELECT 'a':
:text
WHERE 1 =
1
(1 row)
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-05-09 20:51:17 | Re: psql wrapped format default for backslash-d commands |
Previous Message | Kevin Grittner | 2008-05-09 20:47:03 | Re: psql wrapped format default for backslash-d commands |