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

From Michael Paesold
Subject Re: Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed)
Date
Msg-id 00ec01c62e7b$f994ee20$67dc8380@zaphod
Whole thread Raw
In response to Re: FW: PGBuildfarm member snake Branch HEAD Status changed  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Martijn van Oosterhout wrote:

> 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).
>
> 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?

Right, my explanation was not correct. It should have been "the last column 
is now also filled with spaces". Of course all but the last column were 
always filled with spaces.

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

I personally don't like the added spaces (feels inefficient), but that is 
only a matter of taste, so you can rather ignore it.
I am not sure about people who perhaps rely on the output format in scripts 
(even if it's bad to rely on that specific output format, because the output 
of psql can be changed to be more suitable for scripts). For multi-column 
output things have not really changed anyway.

Best Regards,
Michael Paesold 




pgsql-hackers by date:

Previous
From: ohp@pyrenet.fr
Date:
Subject: Re: how is that possible
Next
From: Tom Lane
Date:
Subject: Re: Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed)