Re: Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed) - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed)
Date
Msg-id 20060210193240.GF576@svana.org
Whole thread Raw
In response to Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed)  ("Michael Paesold" <mpaesold@gmx.at>)
Responses Re: Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed)
List pgsql-hackers
On Fri, Feb 10, 2006 at 08:06:53PM +0100, Michael Paesold wrote:
> A side affect of this newline patch is that all fields are now filled with
> white space up to the displayed column width, even for the last (or only
> column). I guess this is somehow required for consistent display.
> Otherwise, it makes copy&paste from a psql session more painful, because of
> all the added white-space. I hope that psql output intended for script
> output using the available flags (i.e. not the "nice display" output) is
> unaffected?

My intention was to only change formatted output. Unformatted should be
unchanged from previous.

The extra spaces is an interesting side-effect. In the past it would
only have worked for the last column anyway, right?

Anyway, it is a fixable issue and I'd consider doing it if people think
it's worth it.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

pgsql-hackers by date:

Previous
From: Ron
Date:
Subject: What do the Windows pg hackers out there like for dev tools?
Next
From: ohp@pyrenet.fr
Date:
Subject: Re: how is that possible