Re: psql wrapped format default for backslash-dcommands

Kevin Grittner wrote:
> >>> On Fri, May 9, 2008 at 3:53 PM, in message
> <200805092053(dot)m49Krq529089(at)momjian(dot)us>, Bruce Momjian
> <bruce(at)momjian(dot)us> wrote:
>
> > test=> \pset format wrapped
> > Output format is wrapped.
> > test=> \pset columns 50
> > Target width for "wrapped" format is 50.
> > test=> explain analyze select * from pg_type, pg_language;
> > QUERY PLAN
> > --------------------------------------------------
> > Nested Loop (cost=1.03..25.86 rows=807 width=66
> > 5) (actual time=0.037..4.528 rows=807 loops=1)
> > -> Seq Scan on pg_type (cost=0.00..8.69 rows
> > =269 width=555) (actual time=0.018..0.377 rows=2
> > 69 loops=1)
> > -> Materialize (cost=1.03..1.06 rows=3 width
> > =110) (actual time=0.001..0.005 rows=3 loops=269
> > )
> > -> Seq Scan on pg_language (cost=0.00.
> > .1.03 rows=3 width=110) (actual time=0.004..0.00
> > 7 rows=3 loops=1)
> > Total runtime: 5.490 ms
> > (5 rows)
> >
> > Of course, running it on a 50-column display in 'aligned' mode isn't
> > going to look good either.
>
> With current production software, if I run in a 50 column window and
> cut and paste into email, there aren't any line-ends in the email as
> there would be with wrapped format.

I think that depends on what terminal you are using, but I do see some
of my terminal programs understand when wrapping happens and adjust the
cut/paste behavior.

--
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. +