From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: explain output infelicity in psql |
Date: | 2009-12-11 01:11:19 |
Message-ID: | 200912110111.nBB1BJN01558@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(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 | Greg Smith | 2009-12-11 01:13:36 | Re: thread safety on clients |
Previous Message | Alvaro Herrera | 2009-12-11 01:09:11 | Re: Viewing table data only from its corresponding oid-named file |