From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: explain output infelicity in psql |
Date: | 2009-12-10 17:08:01 |
Message-ID: | 603c8f070912100908j3ea1d714l1e5eb5d147563e94@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Dec 10, 2009 at 11:44 AM, Ron Mayer
<rm_pg(at)cheapcomplexdevices(dot)com> wrote:
> Alvaro Herrera wrote:
>> Robert Haas escribió:
>>> On first blush, I'm inclined to suggest that the addition of + signs
>>> to mark continuation lines is a misfeature.
>>
>> EXPLAIN is a special case. IMHO it should be dealt with accordingly.
>>
>
> Is it?
>
> Wouldn't it affect anyone who stuck XML in a txt column and wanted
> to copy and paste it into a parser?
>
> Perhaps single column output usually won't want the + signs (because
> it's copy&pasteable) but multi-column output could?
I don't think inconsistency is a good thing here. Apparently the old
format is available via \pset linestyle old-ascii. We can either
decide that people should use that format if they want that behavior,
or we can decide that changing the default was a mistake and revert
it. I don't think a half-way-in-between solution is a good option.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-12-10 17:10:27 | Re: explain output infelicity in psql |
Previous Message | Andrew Dunstan | 2009-12-10 17:07:09 | Re: explain output infelicity in psql |