Re: explain output infelicity in psql - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: explain output infelicity in psql
Date
Msg-id 200912110111.nBB1BJN01558@momjian.us
Whole thread Raw
In response to Re: explain output infelicity in psql  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: explain output infelicity in psql  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Andrew Dunstan wrote:
> 
> 
> Tom Lane wrote:
> > regression=# select
E'xxxxxxx\nxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\nxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
> >     as a, 1 as b;
> >                           a                           | b 
> > ------------------------------------------------------+---
> >  xxxxxxx                                             +| 1
> >  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx                  +| 
> >  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx | 
> > (1 row)
> >
> > regression=# 
> >
> > The point here is exactly that previous versions didn't show the
> > distinction well.
> >
> >             
> >   
> 
> If we really want to make linefeeds visible, I think we should place the 
> indicators immediately after the character preceding the line feed, not 
> next to the column separator.

One idea would be to change the column _separator_ for newlines --- that
way, they don't show up for single-column output.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Viewing table data only from its corresponding oid-named file
Next
From: Greg Smith
Date:
Subject: Re: thread safety on clients