Re: explain output infelicity in psql

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: explain output infelicity in psql
Date: 2009-12-10 17:10:27
Message-ID: 4B20D723020000250002D2FC@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:

>> A simple if ugly hack would make psql use old-ascii print style
>> (which doesn't use these contionuation chars) if the first
>> attribute in the resultset was named 'QUERY PLAN'

> I don't believe that machine-readable EXPLAIN output is the only
> multi-line output value that anyone would ever wish to cut and
> paste into an editor without picking up a lot of stray garbage, so
> I don't think this is a solution.

Agreed.

This would be a significant annoyance for me on a regular basis. If
I can't turn it off, it would probably cause me to create my own
locally patched version of psql. Another alternative would be to
use some other tool to run queries where I wanted long values
without this, but psql has so many nice features that I'd be
switching back and forth, so the patch would probably be easier.

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-12-10 17:23:58 Re: explain output infelicity in psql
Previous Message Robert Haas 2009-12-10 17:08:01 Re: explain output infelicity in psql